# Describe schedule fails

**URL:** <https://community.temporal.io/t/describe-schedule-fails/17214>\
**Category:** Community Support\
**Created:** [April 23, 2025, 1:33pm UTC](https://community.temporal.io/t/describe-schedule-fails/17214 "2025-04-23T13:33:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anton\_Maters\_Twintos](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/anton_maters_twintos/32/7176_2.png) [@Anton\_Maters\_Twintos](https://community.temporal.io/u/Anton_Maters_Twintos)\
**Post date:** [April 23, 2025, 1:33pm UTC](https://community.temporal.io/t/describe-schedule-fails/17214/1 "2025-04-23T13:33:04Z")

</div>

Temporal was running just fine with 2 schedules and around 19k workflow executions.  
During the weekend suddenly retrieving information about a schedule fails.  
We can reproduce it running the admin-tools using:  
temporal --namespace schedule describe --schedule-id \<ID\_OF-SCHEDULE\>  
which results in an error: context deadline exceeded.  
or by going to temporal-web, go to schedules (which works) and select any of the 2 existing schedules.  
Also, in the web interface we can navigate to workflows and see all details there.  
no clue on

## Extra information:

* * *

After execution, these metrics increase:

service\_error\_with\_type{ **container** =“temporal-frontend”, **endpoint** =“metrics”, **error\_type** =“serviceerror\_DeadlineExceeded”, **exported\_namespace** =“twintos”, **instance** =“10.2.1.191:9090”, **job** =“temporal-frontend-headless”, **namespace** =“cluster-temporal”, **operation** =“DescribeSchedule”, **pod** =“temporal-frontend-7487cb4889-z4jqd”, **service** =“temporal-frontend-headless”, **service\_name** =“frontend”, **type** =“frontend”}

service\_error\_with\_type{ **container** =“temporal-history”, **endpoint** =“metrics”, **error\_type** =“context\_DeadlineExceeded”, **exported\_namespace** =“twintos”, **instance** =“10.2.2.149:9090”, **job** =“temporal-history-headless”, **namespace** =“cluster-temporal”, **operation** =“QueryWorkflow”, **pod** =“temporal-history-5979f45bd5-ngxh2”, **service** =“temporal-history-headless”, **service\_name** =“history”, **type** =“history”}

* * *

GRPC\_HEALTH\_PROBE\_VERSION=v0.4.37  
wget -qO grpc\_health\_probe "[https://github.com/grpc-ecosystem/grpc-health-probe/releases/download/${GRPC\_HEALTH\_PROBE\_VERSION}/grpc\_health\_probe-linux-amd64"](https://github.com/grpc-ecosystem/grpc-health-probe/releases/download/$%7BGRPC_HEALTH_PROBE_VERSION%7D/grpc_health_probe-linux-amd64%22)  
chmod +x ./grpc\_health\_probe

temporal operator cluster health --address temporal-frontend:7233  
./grpc\_health\_probe -addr=temporal-frontend:7233 -service=temporal.api.workflowservice.v1.WorkflowService  
./grpc\_health\_probe -addr=temporal-matching-headless:7235 -service=temporal.api.workflowservice.v1.MatchingService  
./grpc\_health\_probe -addr=temporal-history-headless:7234 -service=temporal.api.workflowservice.v1.HistoryService

Inside the admin tools pod gives:

SERVING  
status: SERVING  
status: SERVING  
status: SERVING

* * *

persistence psql schema version: 1.16  
visibility psql schema version: 1.9

temporalio/server:1.27.2  
temporalio/ui:2.37.1

* * *

deploying temporal using helm chart  
version: “0.62.0”  
repository: [https://go.temporal.io/helm-charts](https://go.temporal.io/helm-charts)

* * *

Any help much appreciated

---

<div class="post-metadata">

**Author:** ![emalihins](https://avatars.discourse-cdn.com/v4/letter/e/858c86/32.png) [@emalihins](https://community.temporal.io/u/emalihins)\
**Post date:** [December 16, 2025, 11:08am UTC](https://community.temporal.io/t/describe-schedule-fails/17214/2 "2025-12-16T11:08:39Z")

</div>

Hi @Anton_Maters_Twintos did you ever resolve this?