rewindex

CompaniesTemporal CloudIncidents

Temporal Cloud: Error fetching Schedules count

No impact listedStatus: resolvedStarted Resolved (18 h)1 updatestatus.temporal.io (opens in new tab)

Timeline of updates

  1. resolved

    The UI is working as expected now. We've deployed a fix, and the schedules count API is working as expected.

From Temporal Cloud’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.temporal.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Temporal Cloud, started 2026-02-27 04:18 UTC, resolved after 18 h, 1 update(s).

Title
Error fetching Schedules count
Vendor
Temporal Cloud
Date
URL
https://rewindex.com/company/temporal-cloud/incidents/jr5rbtb5t2vh

Temporal Cloud profileRecent Temporal Cloud incidentsAll outages on February 27, 2026Temporal Cloud in February 2026MarkdownJSON