Understanding where in a function the function is failing is exceptionally difficult just looking at the record history widget even with Error Messaging turned on. We had a function supposedly run 5 times, the first successfully, and then subsequently fail 4 times, but I cannot see record of that.
Hi @rosschul,
We’re actively working to provide deeper granularity and clearer error visibility across all functions and connectors. Aside from the exact step where a function fails, what other info would help you debug faster? Are you looking variable states or just a more reliable log of every attempt?
Best,
Cana
Looking for a reliable log of all attempts or even if we could select branches where we would like a log taken if it goes down a specific logic path that would be extremely useful.
We are facing a race condition when creating units in a function that are sequentially serialized. Being able to see when each function step was executed just like the test would allow better debugging.
Any update on this request? Having deeper visibility into how the functions are running and if they are failing would be extremely helpful.
Thanks,
Ross