Hey guys.
Currently I can only pass a failure message to the “post failure” method (https://docs.camunda.org/manual/7.4/reference/rest/external-task/post-failure/). What do you think of a feature request extending this to allow to hand over a complete stack trace additionally, so it can be displayed in the created incident (comparable to what we do with failed jobs)?
Cheers
Bernd
Hi Bernd,
I think it would be nice to have the possibility to provide a detailed error report.
Yet, I am not sure if a String field is the best solution. Depending on your scenario, the error report may have a structure and that structure could be processed automatically (e.g. a JSON object that identifies the machine that processed the external task, its workload when the error occurred, etc.). In such a case, providing a TypedValue (e.g. Spin JSON) would be much nicer.
Not sure how that would work together with a generic Incident application that displays errors for both jobs and external tasks, but from the external task perspective I would prefer that.
The poor man’s alternative to that could also be allowing variables to be submitted on the handleFailure call which can contain any error information.
Cheers,
Thorben
Hi Thorben.
Having a typed value would make it more powerful, but I think that is not even necessary. From my perspective it is more important to have it aligned with Failed Jobs when creating incidents. Then it does not matter from a monitoring/alarming perspective if an incident was caused by an “internal” or external service task.
I created https://app.camunda.com/jira/browse/CAM-5701 for tracking.
Proposed AT:
Cheers
Bernd