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
Open Source.
Open source hosted in AWS with Redis as queue provider.
What steps can we follow to reproduce the behaviour?
Configuring the forward statement option to go into an endpoint, then check the results on said endpoint.
What is the actual behaviour?
When we use the forward statement logic, instead of receiving one POST request in our system, we're receiving two. The first one lacks the person property entirely, with the second event having that property with its right data.
Additionally, we found that when we restarted the Worker (or sometimes), a single event was sent rather than two. It seems there is a race condition within the queues.
What is the expected behavior?
When we use the forward statement logic, we receive a single POST request with all the filled fields.
Is there any additional information that will help us replicate/understand the problem?
We have retrieved the API logs on when an event is sent once, and then when the event is sent twice:
What version were you using?
Open Source.
Open source hosted in AWS with Redis as queue provider.
What steps can we follow to reproduce the behaviour?
Configuring the forward statement option to go into an endpoint, then check the results on said endpoint.
What is the actual behaviour?
When we use the forward statement logic, instead of receiving one POST request in our system, we're receiving two. The first one lacks the
person
property entirely, with the second event having that property with its right data.Additionally, we found that when we restarted the Worker (or sometimes), a single event was sent rather than two. It seems there is a race condition within the queues.
What is the expected behavior?
When we use the forward statement logic, we receive a single POST request with all the filled fields.
Is there any additional information that will help us replicate/understand the problem?
We have retrieved the API logs on when an event is sent once, and then when the event is sent twice:
Worker log when it's being sent once:
Worker log when it's being sent twice:
The text was updated successfully, but these errors were encountered: