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:/...

Hi @rohandhakad: I believe the org (1161908) against which you are trying to create a registration is a production org, whereas in your screenshot I can see that you are using https://api-stage.adobe.io, which represents stage environment.Most probably that's why you are getting the api-key is inval...

Hi @tatrived. This question does not seem relevant to the Adobe I/O Events forum. I would request to ask about this in the AEM community please.