In addition to `Task` having a `TimeoutSeconds` and `TimeoutSecondsPath`, the top-level `StateMachine` also has a `TimeoutSeconds` (but not Path interestingly) This specifies the maximum time the entire state machine can run before raising a `States.Timeout` error. [[ref]](https://docs.aws.amazon.com/step-functions/latest/dg/statemachine-structure.html) <!-- 1. Describe the issue you are having and what you expected to happen. --> <!-- 2. Describe the steps to reproduce, including any log snippets and stack traces that will help diagnose. --> <!-- 3. Describe your environment, including - Version - Environment - For ManageIQ: e.g. VMware appliance, EC2 appliance, Monolithic container, Kubernetes operator, etc - For gems: e.g. `gem env`, `bundle env`, `ruby -v`, etc --> <!-- 4. Ask @miq-bot to apply additional labels, reviewers, or assignees. (As described in https://github.com/ManageIQ/miq_bot#requested-tasks) e.g. `@miq-bot add-label label_name` `@miq-bot add-reviewer @name` -->
In addition to
Taskhaving aTimeoutSecondsandTimeoutSecondsPath, the top-levelStateMachinealso has aTimeoutSeconds(but not Path interestingly)This specifies the maximum time the entire state machine can run before raising a
States.Timeouterror.[ref]