it would be nice if the console errors has a reference to the block which caused the error
1 Like
I find it hard to troubleshoot a scheduled flow when it encounters an error, it just states the element name where there could be number of the same elemnt in my flow. It would be helpful if it could point out which exact element was the error encountered. Specially when the error message is also not adding any clue…
Hello
Debugging in ElectroNeek can be frustrating when error messages don’t reference the specific block that caused the issue. A more detailed error output, including the exact workflow step, would make troubleshooting much easier.
One potential workaround is to use log messages strategically throughout the workflow. By adding logging at key points (before and after critical actions), you can narrow down where the failure occurs. Additionally, enabling detailed logs in Studio Pro might provide more context.
It would be great if ElectroNeek could introduce error tracing that highlights the exact block in the workflow diagram when an error occurs. Have you tried reaching out to their support team about this? Maybe they have upcoming improvements in this area.