# Nested Workflow Timeout

**URL:** <https://forums.losant.com/t/nested-workflow-timeout/5801>\
**Category:** Help\
**Tags:** workflow\
**Created:** [March 12, 2025, 12:40pm UTC](https://forums.losant.com/t/nested-workflow-timeout/5801 "2025-03-12T12:40:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Walton](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jason_walton/32/5023_2.png) [@Jason\_Walton](https://forums.losant.com/u/Jason_Walton)\
**Post date:** [March 12, 2025, 12:40pm UTC](https://forums.losant.com/t/nested-workflow-timeout/5801/1 "2025-03-12T12:40:26Z")

</div>

In this example from the documentation, is the called workflow subject to the 60 second timeout of the calling workflow? I’m assuming yes, but thought I’d ask.

 ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/8/82296dac40e522f8b6b3b14b8fb96de44db1442f.png)

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [March 12, 2025, 1:30pm UTC](https://forums.losant.com/t/nested-workflow-timeout/5801/2 "2025-03-12T13:30:32Z")

</div>

It is not actually; the [Workflow Trigger Node](https://docs.losant.com/workflows/outputs/workflow-trigger/) queues a new, separate workflow run that has its own 60-second timeout limit.

---

<div class="post-metadata">

**Author:** ![Jason\_Walton](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jason_walton/32/5023_2.png) [@Jason\_Walton](https://forums.losant.com/u/Jason_Walton)\
**Post date:** [March 12, 2025, 3:38pm UTC](https://forums.losant.com/t/nested-workflow-timeout/5801/3 "2025-03-12T15:38:21Z")

</div>

Thanks for the quick reply Dylan, I was hoping for that answer.