I have misconfigured a lambda call within a step function waitForTaskToken pattern, as in
<code>"Payload": {
"taskToken": "$$.Task.Token",
"field1": "blah"
}
</code>
<code>"Payload": {
"taskToken": "$$.Task.Token",
"field1": "blah"
}
</code>
"Payload": {
"taskToken": "$$.Task.Token",
"field1": "blah"
}
instead of
<code>"Payload": {
"taskToken.$": "$$.Task.Token",
"field1": "blah"
}
</code>
<code>"Payload": {
"taskToken.$": "$$.Task.Token",
"field1": "blah"
}
</code>
"Payload": {
"taskToken.$": "$$.Task.Token",
"field1": "blah"
}
And the value of the task token seems to be lost forever, because I can’t find it anywhere. And the step is now hanging as Running. I don’t have permissions to terminate the execution, but I have a lambda that accepts a task token and sends task success. How do I get the token now?
AWS CLI get-execution-history doesn’t have it, AWS Console doesn’t have it in ANY of the inputs or outputs. They all just say “yeah, sure, here is your input to the step, it’s “taskToken”: “$$.Task.Token”,
Which, as you can imagine, isn’t terribly helpful. I expected some way to map execution id and a step to a task token.