# Schedules in Global Namespaces

**URL:** <https://community.temporal.io/t/schedules-in-global-namespaces/8790>\
**Category:** Community Support\
**Tags:** java-sdk, namespace\
**Created:** [July 10, 2023, 2:08pm UTC](https://community.temporal.io/t/schedules-in-global-namespaces/8790 "2023-07-10T14:08:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonatmil](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@jonatmil](https://community.temporal.io/u/jonatmil)\
**Post date:** [July 10, 2023, 2:08pm UTC](https://community.temporal.io/t/schedules-in-global-namespaces/8790/1 "2023-07-10T14:08:39Z")

</div>

How is it recommended to use a Schedule in Global Namespaces i.e., where should they be created to reach expected behavior during failover? Also, what is expected behavior of Schedules in the wake of a failover in Global Namespaces?

Thanks

---

<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:** [July 17, 2023, 2:01am UTC](https://community.temporal.io/t/schedules-in-global-namespaces/8790/2 "2023-07-17T02:01:15Z")

</div>

Hi, I think you got answer on this question on Slack, but just for reference:  
There should not be issues that are specific to schedules and cluster replication. Schedules are replicated just like workflow executions.