# Will setting StartToClose lead to non-determinism in Python?

**URL:** <https://community.temporal.io/t/will-setting-starttoclose-lead-to-non-determinism-in-python/9536>\
**Category:** Community Support\
**Tags:** python-sdk, timeout\
**Created:** [September 19, 2023, 12:28pm UTC](https://community.temporal.io/t/will-setting-starttoclose-lead-to-non-determinism-in-python/9536 "2023-09-19T12:28:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wahib](https://avatars.discourse-cdn.com/v4/letter/w/b5a626/32.png) [@wahib](https://community.temporal.io/u/wahib)\
**Post date:** [September 19, 2023, 12:28pm UTC](https://community.temporal.io/t/will-setting-starttoclose-lead-to-non-determinism-in-python/9536/1 "2023-09-19T12:28:29Z")

</div>

Hi, we forgot to set the StartToClose timeout for our activities (the ScheduleToClose timeout was set though) and now we have a bunch of running workflows. If we were to add the StartToClose timeout in our logic now, will that lead to non-determinism in the currently active workflows?

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [September 19, 2023, 1:31pm UTC](https://community.temporal.io/t/will-setting-starttoclose-lead-to-non-determinism-in-python/9536/2 "2023-09-19T13:31:06Z")

</div>

It should not but for pending activities it would have no effect as their ActivityTaskScheduled event is already recorded in event history.  
Note that if you only set ScheduleToClose timeout, StartToClose will be set to same value.
