@Swap2357: Could you provide more details about your Developer Console project, particularly the event registration that is causing the retries? Sharing the URL would help.Also have you tried looking at the Debug Tracing tab to see what could be the cause of these retries?

@ShubhamAg2 Can you share more details?Environment: stage/prodCommerce instance idDeveloper console URL for event registrationTime frame on when this was happeningThis will help us in debugging this further.

The 500 error is coming from the Runtime action. I/O Events attempts to deliver the event, and if it encounters a 5xx error, it retries. What you're likely seeing is the event being retried.

You can do the below:1. Ensure that the consumer application is processing events successfully and is returning 2XX response.2. Once the consumer application is restored, please update your event registration on Developer Console to reset its status.

Hi @Eugene_Kapelko, Can you please share the event registration URL from developer console? I noticed you have masked out those details but having the URL would be helpful for us to debug. Also what is the documentation you are referring to?1) I created an event as in the documentation: 

I am not sure if you landed on the right forum, but this is not the right place for this question.

Hi @Abie,This is not the right forum for this question. Please ask in the AEM Assets community forum. Hope that helps!

Hi @Ajit_Tr. I don't think this is the right forum for this question.Can you please try Adobe Campaign Standard / Adobe Campaign Classic v7 & Campaign v8 forums instead.

You can use the journaling API instead, but you'll have to keep track of a position marker to fetch events since that "position".

Stage workspace does not correspond to staging environment. Please try your call with https://api.adobe.io/events as the base URL and it should work.For posterity, I am listing down the different URLs per environment:API Management Facade Base URLStage: https://api-stage.adobe.io/eventsProd: https:/...