Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task Catch/Error Handling #3

Open
totherik opened this issue Apr 5, 2017 · 0 comments
Open

Task Catch/Error Handling #3

totherik opened this issue Apr 5, 2017 · 0 comments

Comments

@totherik
Copy link
Owner

totherik commented Apr 5, 2017

When a Task is executed the Resource returns information as to the nature of the failure. According to the specification any error that is transferred to another state is an Error Output type containing an "Error Name" (named "Error") and optional "Cause" property.

When a state reports an error and it matches a Catcher, causing a transfer to another state, the state’s result (and thus the input to the state identified in the Catcher’s “Next” field) is a JSON object, called the Error Output. The Error Output MUST have a string-valued field named “Error”, containing the Error Name. It SHOULD have a string-valued field named “Cause”, containing human-readable text about the error.

So, if a Catcher has a ResultPath and can pluck the appropriately-formatted Error Output from the Result, everything is fine as long as the returned resource conforms to the Error Output specification. What's not clear is how to map the Task result to Error Output if no ResultPath is defined.

This needs to be codified and implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant