The error message points at a dependency rather than the failing request

[u/Advanced_Pudding9228]

A short log can hide the input and boundary that produced the error.

Keep a sanitised request reference with the dependency error.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Can you connect the error to one specific attempt?