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
With the current solution, it is only possible to match producer and consumed messages using the key from the sent message. However, in our project, we have an internal key change from produced and consumed messages. This means that with the current implementation we are not able to bind produced messages to consumed one. Therefore Gatling is always returning that the whole flow hasn't been successfully finished.
To solve this issue It can be possible to match consumed and produced messages using some customizable headers, such as correlation-id.
The test scenario would look like snipped below after adding the configurable Headers option: