Turns out I may have found the answer, unseemly as it may be. The error message appears to be bogus. The developer went back and checked the stored procedure and it had been updated, despite the error message.