Idea Summary
APEX Human Task allows you to define Actions for almost every state transition of a task instance except for a task reaching Errored state.  Please add support for Errored.

Use Case
When an APEX Human Task is a used as step in a larger process, the existing Task Actions allow you to call back the process manager in the cases when the APEX task stops because it completes, expires, and is cancelled.  This leaves 1 final state that doesn't have a Task Action - the Errored state.  So you can't always get a call back when a task finishes.

Why is this important?   When we call an APEX Human Task as a step in a Flows for APEX workflow, the APEX task can notify the workflow engine that it is finished when the task completes, expires or is cancelled.  (we have a task Action plugin that returns task state and outcome).   But if the task errors, there is no way to notify the workflow engine that the task has errored (short of periodically polling for errors).  For customers who are managing their business processes from the workflow, they can't then see that the workflow is stuck because of a task error on an APEX Human Task.

Preferred Solution (Optional)
Please extend the Task Actions to allow an action to be defined on the ERRORED state.