Skip to content

fix(aws-sfn): reject StartSyncExecution on STANDARD state machines - #1689

Merged
NitinKumar004 merged 1 commit into
developmentfrom
fix/sfn-parity-1473
Oct 23, 2026
Merged

NitinKumar004 merged 1 commit into
developmentfrom
fix/sfn-parity-1473

Conversation

@NitinKumar004

Copy link
Copy Markdown
Collaborator

StartSyncExecution now returns StateMachineTypeNotSupported for a STANDARD state machine, matching real Step Functions, which offers synchronous executions for EXPRESS workflows only. The type check runs after the existence check, so a missing state machine is still StateMachineDoesNotExist.

StopExecution on an execution that has already closed keeps its current behavior (200 with the original stopDate, no state change). AWS documents no error for this case, so the behavior is pinned with a test and a code comment and listed under the SFN non-goals.

Tests that called StartSyncExecution on STANDARD machines now use EXPRESS machines, including the Task and Parallel recursion-guard tests. New provider and SDK wire tests cover both machine types.

Part of #1473

@NitinKumar004
NitinKumar004 merged commit 020ead9 into development Oct 23, 2026
23 checks passed
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

Successfully merging this pull request may close these issues.

1 participant