Users can use a new FailTask command to signal a task failed (for example, the API was not available), the interpreter then returns either a TaskFailed event with the amount of time to wait before resuming execution, or it will transition according to the Catch rule.
What kind of change does this PR introduce?
This PR adds support for failing task activities.
What is the new behavior?
Users can use a new
FailTaskcommand to signal a task failed (for example, the API was not available), the interpreter then returns either aTaskFailedevent with the amount of time to wait before resuming execution, or it will transition according to the Catch rule.