Zapier: Redis cache maintenance: redis-production and trigger-subscriptions
Affected components: Polling TriggersPolling TriggersPolling TriggersPolling Triggers
Timeline of updates
- maintenance scheduled
Zaps that use polling triggers are temporarily delayed while we perform scheduled infrastructure maintenance. We have paused polling during the upgrade; this pause is expected to last approximately 30 minutes. Our team is carrying out the upgrade and checking service health before resuming polling.
- maintenance in progress
Scheduled infrastructure maintenance is in progress. Polling is temporarily paused during the upgrade, delaying Zaps that use polling triggers. We are carrying out the upgrade and will check service health before resuming polling.
- maintenance in progress
We are extending the polling pause by an additional 30 minutes as scheduled maintenance continues. Zaps that use polling triggers will continue to experience delays during this extension. We apologize for the continued disruption.
- maintenance in progress
We are gradually re-enabling polling so Zaps that use polling triggers can begin catching up while maintenance continues. Polling is currently running at reduced capacity, so delays will continue during this process. We are monitoring performance as we restore polling.
- maintenance complete
Maintenance is complete, and polling has been fully re-enabled. Zaps that use polling triggers are running at normal capacity again. We are continuing to monitor service health and replaying potentially affected tasks. We apologize for the extended delays and thank you for your patience.
Changes Rewindex caught on this incident
- Incident updated: Redis cache maintenance: redis-production and trigger-subscriptions
- Incident updated: Redis cache maintenance: redis-production and trigger-subscriptions
- Incident updated: Redis cache maintenance: redis-production and trigger-subscriptions
- Incident updated: Redis cache maintenance: redis-production and trigger-subscriptions
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7f1678aac7da1111…Version 2 captured
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1d75a1c0fa30732a…Version 3 captured
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
224fb3422c4cfd5c…Version 4 captured
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
05f20e69a5bd494f…Version 5 captured
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a2ee821abc2b5a00…
Impact, status and times are the vendor’s own, as last archived. View on status.zapier.com (opens in new tab).
Cite this
Maintenance posted by Zapier, started 2026-10-24 13:00 UTC, not resolved, 5 update(s); edited after publishing.
- Title
- Redis cache maintenance: redis-production and trigger-subscriptions
- Vendor
- Zapier
- Date
- URL
- https://rewindex.com/company/zapier/incidents/01M5Q5JNDA7JY3D62FCA8N8HCG
Zapier profileRecent Zapier incidentsAll outages on October 24, 2026Zapier in October 2026MarkdownJSON