Hi,
When performing an action without For each loop, if 400 error happens, we can see why it happened, e.g.:
However, if exception happens in a For each… loop, like this:
we don’t get any details about why the exception happened:
Is it possible to make exception details available for For each… loops?
CC @paul_n if we are missing something and there is a new way to provide details on why we intentionally did not process workflow action, can you please let us know what’s the proper way of doing that at this moment?
Thanks, we are investigating that
Hi Paul, is there any info on this? We are continuing to receive support requests from merchants who are asking for help in understanding the reason of 400 exception codes. Returning them to workflow run details will be very helpful. Thank you in advance!
This will eventually get fixed, yes.
Hi @paul_n , it’s been 3 months since the problem started affecting merchants whose workflow run actions were unable to be processed – they’re unable to see the reason of HTTP 400 response we make directly in Flow run details. We are currently investigating this through support individually for each case, which isn’t a great UX for merchants. Do you have any ETA on this? Will appreciate your help.
A fix is definitely needed for this! It’s very hard to debug a workflow or know how to respond if there are no details.
We weren’t able to pick up fixing this right away. We are investigating to see if we can do a quick fix on it.
This fix for this is deployed now
