Event processing failed (attempt 283)

[fedealconada]

Hi, I can see a lot of these logs

Event processing failed - id: qMefqQjU3c - topic_id: 0x5e09…e084. Retrying... (attempt 283). Error: Slack error: Slack API error: ratelimited

Is the error just because we are getting rate limited? Or the error is originally coming from elsewhere?

[joshstevens19]

yeah this is happening as you got slack enabled and it has failed to send due to rate limiting with slack - atm it will fail fully if the slack can not push - are you indexing data as well as pushing messages at same time?

[fedealconada]

But does it keep retrying forever?On 8 Jan 2025, at 14:53, Josh Stevens ***@***.***> wrote: yeah this is happening as you got slack enabled and it has failed to send due to rate limiting with slack —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[joshstevens19]

Yes it will forever keep retrying it assumes in these cases the node or whatever is temp down so it is as strict as possible and just keeps going back again and again.. in this case you want it to fail and move on? I could add a setting in the streams to fire and forget

[fedealconada]

I'm not really sure... actually, I'm not sure why it fails because I only see the error from Slack... The thing is that, if it's constantly failing and it's trying to send a Slack alert and I'm being rate limited, but we keep sending alerts to Slack, the rate limit issue never stops...

[joshstevens19]

lol yeah i guess i could add a config of fire and forget on the streams so if it rate limits it continues

[fedealconada]

it could also be good to have both graphql limit and timeout configurable via env vars...

[joshstevens19]

Ah on you raised another ticket on this yes sure happy to add