Norman Hooghof

The 2 examples work fine on next now. The next new examples give an error or an unexpected response. # EXAMPLE 3 ### Input header name: uuid value: 7cbf5a21-0e95-4df0-80c8-34f2c56d2032 ###...

Concerning example 3, the frontend shows the expected body. The header ''uuid' is in the incoming message. If you call the flow, the body stays empty.   The jsonslurper...

**Test on next** The time between the first and the last exchange is expected to be 3 minutes.   **Test on acceptance***  

I changed the test. If the socket timeout is larger than the delay on the requested api, the response is right. If the socket response is shorter than the delay...

On 3 and 4 July it still works fine.

I spotted this related frontend regression: https://github.com/dovetailworld/front-end/issues/4418

In principle, the retry mechanism works fine in functional sense. The used number of retries and the timeout on retry work as expected. There are a few remarks 1. Number...

Concerning 3. Response on Request-Reply, I created 2 test flows (next, microscope, http retry, flows: HTTP retry flow and 502 error flow. **Conclusions** - As expected, after a 5xx response...