Procedure does not exist -- when it does.

[Carl Roberts]

I have an application where it is critical that a certain stored procedure runs each morning for my clients, each day. For the past five days, though, I have been receiving an error (that I email myself) that the stored procedure does not exist, for each schema.

However, the procedure DOES exist, and when I run the cron job manually, it runs perfect. Is there a known issue where stored procedures just stop existing, or any thoughts on a reason why?

It's created correctly, with the correct privileges, table names, etc.; works flawlessly when run through the cron job (same exact code it gets the error on), and manually through a MySQL client.