Starting from this discussion https://github.com/parodos-dev/serverless-workflow-examples/pull/10#discussion_r1378622244

Since this is an async task, even if we model dedicated states to handle the failures, the final workflow state should be COMPLETED, so:

1. how can we get the user's attention to identify it as a failed flow instead?
2. how can we visualize the diagnostics (error cause + troubleshooting message), inside the data/variables section of the selected workflow or a dedicated section would be more relevant?
3. are you thinking to use the notification service to inform the users? In this case, it'd be great if the orchestrator could do that for all the errors it detects (from data-index?), instead of having each SWF implementing a call to the notification service.