Workflows: Email sending currently delayed
We've caught up on all Workflow emails.
The latest update from PostHog.
State
Resolved
Started
53 d ago
2026-09-09 14:42 UTC
Lasted
2 h 34 min
until 2026-09-09 17:16 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
18 min 12%
Identified
12 min 8%
Monitoring
1 h 41 min 66%
Resolved
23 min 15%
Updates
Times in UTCAs posted by PostHog
We've caught up on all Workflow emails.
We're still working through the backlog of emails - we're monitoring and will update this incident once we've caught up. You can monitor progress of individual workflows from the 'invocations' tab of the workflow in PostHog - delayed runs will transition from 'Running' to 'Succeeded' once complete.
Whilst the temporary fix worked we have meanwhile taken action and hardened our systems so this kind of poison pill problem can't happen again. The email queue will drain and some emails will arrive later but no data was lost.
We fixed the underlying issue and email sending is proceeding normally again. Emails will be delayed. We are monitoring the fix and taking action to avoid a poison pill like this to happen again.
We found the culprit which turns out to be a poison pill entry in our email queue which blocks the queue from proceeding. We are taking steps to resolve this issue.
Email sending is currently delayed. We are investigating the issue. No data is lost.
Affected components
1PostHog in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
21
Median duration
1 h 14 min
This incident
2.1× the median
Other PostHog incidents
All incidentsPostHog·Agents: elevated GitHub error rates
We’ve deployed a mitigation for transient GitHub errors and haven’t observed further failures since.
PostHog·Application: partial outage
All services have returned to normal.
PostHog·PostHog AI connections
This issue has been resolved. PostHog AI and other services are back to normal. Apologies for the interruption.
PostHog·Google Ads Data Warehouse source - some schemas are failing to sync
We've released a fix for this - affected Google Ads tables will catch up automatically at their next scheduled sync, or you can trigger a refresh manually to update the tables sooner.
PostHog·Warehouse sources delayed imports
Warehouse sources backlog has been processed
Follow PostHog
Your coding agent knows when PostHog is down, and tells you when a failure is theirs, not yours. You can also get PostHog incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "posthog" and tell me if PostHog has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=posthog/feed subscribe https://outages.live/feed.xml?providers=posthogFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane