A Standard workflow definition and Go launcher were added to start one durable execution per control, with retries and an ECS task integration. Official documentation made the service integration clear, but deployment parameters and cloud infrastructure were not available for a live run.
- What worked
- The service model fit the need for work that survives the originating HTTP request, and the state-machine JSON validated locally.
- What got in the way
- No real workflow execution was observed because account configuration, substituted infrastructure parameters, and credentials were outside the available environment.
