You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having some trouble with the delay agent. I'm using that to rate limit how many requests are sent to a webhook at once (5 at a time with an interval of 2 minutes). Sometimes, the same number of events in do not get emitted from the delay agent to the post agent (see screenshot). Is there a way to figure out why this is failing intermittently? TBH, I haven't kept a close eye on it and just noticed it again today. Re-emitting a skipped event causes it to process correctly.
Are you using multiple delayed_job background processors? I think it is possible that an Event is dropped when the Agent is ran simultaneously on two processors. If that is the case the root cause would be similar to #2389
I think the only way to resolve the issue is to introduce a lock that ensures that Agents which modify the memory do not run on two different delayed job processes at the same time.
I'm having some trouble with the delay agent. I'm using that to rate limit how many requests are sent to a webhook at once (5 at a time with an interval of 2 minutes). Sometimes, the same number of events in do not get emitted from the delay agent to the post agent (see screenshot). Is there a way to figure out why this is failing intermittently? TBH, I haven't kept a close eye on it and just noticed it again today. Re-emitting a skipped event causes it to process correctly.
Screenshot and agent configs:
The text was updated successfully, but these errors were encountered: