Hi there,
We would like to provide additional information to errors, I am wondering about the ‘proper’ way to add additional information to error reporting,
As an example I have an error report that I could regex to match parts of a log that I can give specific troubleshooting procedures to a user, how would I insert that? I would like the solve to be ‘transportable/not lost’ when updating Deadline.
Thanks,
Marty
Depends on how you’d be presenting this to the user. You could use a Job Report script if you’re having the user manually trigger the process.
And so long as your code goes into DeadlineRepository10\custom it won’t be touched as a part of an upgrade. Anything in there will be used instead of the default code we ship.
Let us know what you think, I’m sure there’s a bunch of ways to do this so your workflow is going to be the director.
Thanks for your reply Justin, I can see how I would add an additional option for the right click Scripts —> {your newly create script}
However, ideally I would prefer tailoring the resulting ‘Error’ info in the right click —> task reports to include the required information.
Is that possible? added a screenshot for context.
That’ll be more difficult, you’d have to change all the FailRender calls to be passed your troubleshooting steps instead of whatever line triggered the error. Which wouldn’t cover failures in the exit code like in your screenshot. And that’s just a guess at it - I’m sure there’s other bits I’m overlooking.
You could have an OnJobError Event Plugin that takes in the error report and writes out troubleshooting steps. It would create a second task report that users could look at for instruction, and be much simpler to implement.
