Error Handling
in progress
Jamie Moore
When a workflow fails, it would be better to get more information delivered with the error. Including, what workflow failed and where it failed. We can handle it halfway by pulling the results link into the error. If you could see the name of the workflow alongside the GUID it would be useful.
Log In
D
Dan Knutson
in progress
This is now in progress - stay tuned.
Jim-Barry Behar
Not to hijack a thread, but I think it would go a very long way towards saving time if the offending object was linked beside the error. Too often, you spend time looking for or reverse engineering the source of the error. Particularly if there are many references to the ID/GUID of the offending object within the source of a workflow.
Spending a lot of time to track down the culprit when the source is known and can linked would save all Rewst-ers a lot of valuable time.
Thank you Alden Wilson for the bailout finding that my culprit was hiding in plain sight as an error in the syntax of an Output Variable (the text of which is not visible when you edit the base workflow).
Alden Wilson
Jim-Barry Behar: Not a solution per se, but the "Edit Workflow" should definitely show triggers, input, and output variables - since they're all part of the workflow.