fix(step-functions): serialize Task timeout as TimeoutSeconds, not Timeout - #6966
Open
jakubknejzlik wants to merge 1 commit into
Open
fix(step-functions): serialize Task timeout as TimeoutSeconds, not Timeout#6966jakubknejzlik wants to merge 1 commit into
jakubknejzlik wants to merge 1 commit into
Conversation
…meout The Task state's toJSON() serialized the timeout arg under the ASL key Timeout, which is not a valid Amazon States Language field name in either JSONPath or JSONata query language mode. Per the AWS Step Functions Task state docs, the correct field is TimeoutSeconds (with TimeoutSecondsPath as the JSONPath-only dynamic variant). Any state machine using timeout on a Task (lambdaInvoke, sqsSendMessage, etc.) currently fails to deploy with: ERROR (SCHEMA_VALIDATION_FAILED): Field 'Timeout' is not supported Renaming the serialized key to TimeoutSeconds fixes the deploy and the timeout behaves correctly at runtime (verified: a Task with a 3s timeout racing a 6s Lambda sleep now deploys cleanly and fails with States.Timeout as expected).
jakubknejzlik
pushed a commit
to jakubknejzlik/stepforge-brain
that referenced
this pull request
Aug 11, 2026
jakubknejzlik
pushed a commit
to jakubknejzlik/stepforge-brain
that referenced
this pull request
Aug 12, 2026
Promoted [MEM-11] correction of MEM-4's root cause (SST timeout serialization bug, upstream PR anomalyco/sst#6966) into semantic memory, closed out the campaign episodic record, cycled MEM-1 OBSOLETE->REMOVED, archived TODAY.md, and regenerated SUMMARY.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
jakubknejzlik
pushed a commit
to jakubknejzlik/stepforge-brain
that referenced
this pull request
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
Taskstate'stoJSON()serializes thetimeoutarg under the ASL keyTimeout, which is not a valid Amazon States Language field name in either JSONPath or JSONata query language mode. Per the AWS Step Functions Task state docs, the correct field isTimeoutSeconds(withTimeoutSecondsPathas the JSONPath-only dynamic variant).Repro (before fix):
sst deployfails with:Fix: rename the serialized key from
TimeouttoTimeoutSeconds.Verified: deployed a state machine with a 3s Task timeout racing a 6s Lambda sleep. Before the fix, deploy fails as above. After the fix, deploy succeeds and the execution correctly fails with
States.Timeoutat runtime, confirmed viadescribe-execution.