Why does my subscription show errors when it delivers events?

Subscription events were created, but errors are received when events are delivered to your Code Engine application or job.

Check to see whether one of the following cases is true.

1. Does the subscription destination application or job exist?
2. Is the destination app or job prepared and looking for HTTP POST messages?

Look at the subscription source to see whether any error messages are returned. For IBM Cloud Object Storage subscriptions, use the ibmcloud ce sub cos get --name SUB_NAME command. For cron subscriptions, use ibmcloud ce sub cron get --name SUB_NAME command.

1. Confirm that your subscription destination exists.

   • If your subscription destination is an application, use the ibmcloud ce app list command to confirm that your application exists and that it wasn't deleted. Check that the status of your application is Ready. You can also use the ibmcloud ce app get command to display the status of the application.
   • If your subscription destination is a job, use the ibmcloud ce job list command to confirm that your job exists. You can also use the ibmcloud ce job get command to display the status of the job.

   For more information about Object Storage subscriptions, see Working with the Object Storage event producer. For more information about cron subscriptions, see Working with the cron event producer.

2. The error message that your subscription source receives might include a 404 Not Found error or a 5xx HTTP error. If you receive either of these errors, then confirm that your destination application is expecting to receive event information as POST HTTP requests. Event information is received as POST HTTP requests for applications and as environment variables for jobs.

If these solutions do not solve your issue, retrieve the logs of your subscription destination application or job. For apps, use the ibmcloud ce app logs command. For jobs, use the ibmcloud ce jobrun logs command to obtain the logs for your specific jobrun.

If these solutions do not solve your issue, try one of the resources in getting support.