RESOURCE_NOT_FOUND
Should you try again? No. Sending it again as is fails the same way.
Why it happens
- The URL path is wrong.
- No object with that ID exists on your account, such as a message ID from another account.
How to fix it
- Check the URL path against the API reference.
- Check that the ID in the path is correct and belongs to your account.
Technical details
For the error format and how to handle it, see Request errors.