DescribeSchedule timeouts on passive cluster

Community Support
1

Hi,

we have cross DC setup and noticed, that DescribeSchedule times out on passive cluster and we are getting:

unable to describe schedule: rpc error: code = DeadlineExceeded desc = context deadline exceeded

This is for UI, CLI and Go SDK. Active cluster DescribeSchedule requests work well. Workers are deployed in both clusters, in equal capacity. selected-apis-forwarding is enabled:

`dcRedirectionPolicy:
  policy: selected-apis-forwarding
  toDC: ""`

Let me know if you have any tips to debug this and whether this is fixable. Temporal server version is 1.22.7, with MySQL (Vitess) and Elasticsearch for visibility.

Kind regards,

Jelizaveta

2

Schedules should be replicated on the standby side, did those schedules exist before you made namespace global?

On the standby side can you search for these scheduler workflows (schedules are just internal workflows)
Via cli or web ui you can for this namespace you set as global use visibility query

TemporalNamespaceDivision = "TemporalScheduler"