You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What went wrong?
I had a state machine definition with a Catch on a Task. When I added a ResultPath to the Catcher I got an error when trying to deploy.
What did you expect should have happened?
I expected deployment to be successful and the catcher to use the ResultPath. Note, this is valid in the the JSON definition that appears in the AWS Console. There shoudn't be an error.
I think that either this should be fixed (to stay in sync with what works in AWS) or a more informative error should be output to save time for anyone who hits this error.
BTW thanks for a great plugin.
The text was updated successfully, but these errors were encountered:
What went wrong?
I had a state machine definition with a
Catch
on aTask
. When I added aResultPath
to the Catcher I got an error when trying to deploy.What did you expect should have happened?
I expected deployment to be successful and the catcher to use the
ResultPath
. Note, this is valid in the the JSON definition that appears in the AWS Console. There shoudn't be an error.What was the config you used?
What stacktrace or error message from your provider did you see?
I got this in the console after running
serverless deploy
Additional Data
Note
I notice in your example there is a
ResultPath
for the state itself. Adding this to my task makes the issue go awayCreateContentfulAsset: { Type: "Task", Next: "PublishContentfulAsset", Resource: { "Fn::GetAtt": ["createImageInContentful", "Arn"], }, Catch: [ { ErrorEquals: ["VersionMismatch"], ResultPath: "$.CreateContentfulAssetError", Next: "AssetAlreadyCreated", }, ], + ResultPath: "$.CreateContentfulAssetResult", },
I think that either this should be fixed (to stay in sync with what works in AWS) or a more informative error should be output to save time for anyone who hits this error.
BTW thanks for a great plugin.
The text was updated successfully, but these errors were encountered: