Loading Profile...
Better error reports when workflows fail.
As workflows get more complex, it also gets more difficult to figure out where they fail (when they fail).
For example: I've been getting fails on this workflow id=097525EEE8DF377AE7A1D785BF71E632 but the activity page does not provide a lot of useful information.
Since the service is in beta, I don't think the users would mind have more debug output (even if less polished).
For example: I've been getting fails on this workflow id=097525EEE8DF377AE7A1D785BF71E632 but the activity page does not provide a lot of useful information.
Since the service is in beta, I don't think the users would mind have more debug output (even if less polished).
I’m anxious
6
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Miguel,
We are currently working on improving the error report. It will be announced on our blog when ready!
Thanks for the feedback!
VR -
Inappropriate?This is a good request and one I asked you about on tarpipe as well. Cool to hear you're working on improving it.
Not sure if there's a public JIRA or Bugzilla where what's been worked on exists but maybe to help you.
1. I would love some sort of toggle on Activities. That is by default it's not verbose but I can make it so if I'm getting failures. This should help with messaging loads.
2. In terms of actual report some useful information would be:
a. What workflow failed - name is good enough
b. source - so email address would be good
c. Error messaging, ideally what connector failed and why
EMPLOYEE
