Menu
I have a step function (illustrated below) and I was working out the few remaining issues when all of a sudden I hit a rather unexpected result:
I'm a bit dumbfounded. Has anyone seen this? Does anyone know how I'd go about troubleshooting it?
506
AWS Step Functions Alternatives Schedule AWS Lambda functions: You can run simple workflows (consisting mainly of one Lambda function) by incorporating the workflow logic into a Lambda function. You can then trigger the function by using an AWS Lambda schedule event.
Step Functions has two workflow types. Standard workflows have exactly-once workflow execution and can run for up to one year. This means that each step in a Standard workflow will execute exactly-once. Express workflows, however, have at-least-once workflow execution and can run for up to five minutes.
Step Functions automatically triggers and tracks each step, and retries when there are errors, so your application executes in order and as expected. Step Functions logs the state of each step, so when things do go wrong, you can diagnose and debug problems quickly.
The developer’s guide to Step Functions states that any state is capable of encountering runtime errors, and these errors can happen for different reasons, including: Issues with state machine definition like no matching rule within a Choice state. Task failures will happen due to an exception within a Lambda function.
Any state can encounter runtime errors. Errors can happen for various reasons: State machine definition issues (for example, no matching rule in a Choice state) By default, when a state reports an error, AWS Step Functions causes the execution to fail entirely.
When a state reports an error and either there is no Retry field, or if retries fail to resolve the error, Step Functions scans through the catchers in the order listed in the array. When the error name appears in the value of a catcher's ErrorEquals field, the state machine transitions to the state named in the Next field.
This may not match your case, but this happens in step functions when you have a Choice state, and the Variable you are referencing is not actually in the state input. You must specify the $.type field.
This may not match your case, but this happens in step functions when you have a Choice state, and the Variable you are referencing is not actually in the state input.
The documentation says:
Note:
You must specify the $.type field. If the state input doesn't contain the $.type field, the execution fails and an error is displayed in the execution history.
but from my experience, you get a Cancelled state.
Have a look here for more info: AWS Step Functions - Choice
74
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
