> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/the-timeout-of-bake-stage-does-not-respect-the-timeout-in-bake-stage-configuration.md).

# The timeout of Bake Stage does not respect the timeout in Bake Stage configuration

### Issue <a href="#issue" id="issue"></a>

Users may notice that although the configuration of `Fail Stage after a specific amount of time` for a bake stage in Spinnaker is set to 4.5 hours:The bake stage does not respect the set timeout limit. It would instead expire before that limit (in this example, 4 hours), although the baking process continues in the environment. The UI would show the following:

### Cause <a href="#cause" id="cause"></a>

The option `Fail stage after a specific amount of time` forces the stage to fail if its running time exceeds a specific length. By default, Spinnaker can use sensible timeouts dependent on the stage type and the operations the stage needs to perform at runtime. These defaults can vary based on chosen configuration. As such, the timeout of bake stage not matching the timeout in the configuration in Spinnaker UI is expected behaviour, as the timeout of the stage may exceed the set maximum time in the Spinnaker Manifest.