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
Output:
Check the Logs and Transactions of the Receiving flow. Try to find the response body of the 5xx statuscode responses that trigger the retry.
Result
Below you see the last response from the Receiving flow in the transactions of the Sending flow. Notice the response body. After the second retry the Receiving flow responds with a 200 statuscode and a response body.
But the 5xx responses also had a body defined that you can't see / evaluate anywhere in the Flow Manager details:
Conclusion
There should be a way to see the response body of 5xx responses. The response body can contain valuable information about why the server responded with a 5xx statuscode. This gives the user a chance to fix underlying issues that cause the 5xx response in the first place.
Maybe we should create an entry in the Logs of the flow for showing the headers and body for each 5xx response?
This issue is related to the response headers that interfere with the retry messages, that is documented in a seperate issue: #269.
There is already a mechanism that logs all relevant information. I assume this isn't probably referenced to the correct flow, so that it's not in log of the flow (only in the general log on the server). We will investigate this.
Body in the entry above is the original body, not the response body. I'm not sure if the response body should be shown there or after ResponseText: in MISSING2?.
Also not sure if the exceptionn is expected in MISSING1?
Summary
You can't find the response body from 5xx responses in the Flow Manager Logs or Transactions of a flow .
Testcase
Dovetail version: 4.17.0-SNAPSHOT-dcb7cc8
Instance: next
Tenant: Regression Tests
Sending Flow: HttpRetrySocketAsynchronous
Flow version: 7
url: https://next.dovetail.world/flowdesigner/66b1efbde56ba4001000012e/7/route
Receiving Flow: HttpRetry500
Flow version: 1
url: https://next.dovetail.world/flowdesigner/66b31c0ee56ba4000e00002f/1/route
Input:
Output:
Check the Logs and Transactions of the Receiving flow. Try to find the response body of the 5xx statuscode responses that trigger the retry.
Result
Below you see the last response from the Receiving flow in the transactions of the Sending flow. Notice the response body. After the second retry the Receiving flow responds with a 200 statuscode and a response body.
But the 5xx responses also had a body defined that you can't see / evaluate anywhere in the Flow Manager details:
Conclusion
There should be a way to see the response body of 5xx responses. The response body can contain valuable information about why the server responded with a 5xx statuscode. This gives the user a chance to fix underlying issues that cause the 5xx response in the first place.
Maybe we should create an entry in the Logs of the flow for showing the headers and body for each 5xx response?
This issue is related to the response headers that interfere with the retry messages, that is documented in a seperate issue: #269.
Original issue on Dovetail Application board: https://github.com/dovetailworld/front-end/issues/4636.
The text was updated successfully, but these errors were encountered: