58 recorded Parabola incidents since November 2019, with official updates, affected components, duration and resolution information.
from 2026-10-05 15:51 UTC to 2026-10-05 15:55 UTC, the Prowork-building web-app was down. It has since recovered and we are monitoring & root-causing to investigate further.
This incident has been resolved.
We are investigating reports of intermittent failure with Prowork chat
We have identified the issue is with our underlying model provider. Retrying chat messages should succeed. We are continuing to investigate.
This incident has been resolved.
We are investigating an issue blocking user-login and some prowork chats, since 2026-09-08 18:10 UTC
We have mitigated the issue as of 2026-09-08 19:41 UTC and are now monitoring
This incident is now resolved: Parabola users faced issues viewing and building flows, from 2026-09-08 2:10-3:41pm EDT (11:10am-12:41pm PDT). We have mitigated the issue fully and are monitoring to make sure future issues don't reoccur. For those users who were building, chatting with Prowork, or kicking off flows manually, a small number of users had individual actions or chats towards building a flow fail. Those users saw a failure in the Parabola web application and should continue building For those users who faced issues such as being logged out, or the webpage-views for flows not showing up, the issues were intermittent during this window, and users can continue with their work.
We have identified slowness in Prowork chat completion and are continuing to investigate the impact from upstream providers on our service.
This incident has been resolved
We have identified slowness in Prowork chat completion and are continuing to investigate
Prowork chats are now running normally
We are investigating reports of Prowork chat slowness.
We have identified Prowork chat slowness and are pursuing changes to fix it.
A fix has been deployed as of 2026-08-03 17:40 UTC (1:40pm EDT; 10:40am PDT) -- we are monitoring to ensure prowork chats continue to improve.
This incident has been resolved.
Team is working on a resolution
Prowork chat is recovering.
Issue resolved
Prowork chat is not responsive for many users. The incident is under investigation.
Prowork chat has been unresponsive for many users starting at 2026-07-29 15:58 UTC. As of 2026-07-29 17:29 UTC, we have mitigated the issue but continue to monitor for a stable, full resolution.
Prowork chat was unresponsive for many users from 2026-07-29 15:58-17:29 UTC. We have mitigated and resolved the issue, and will continue a retrospective root-cause to improve future stability.
We are investigating reports of issues with the Custom Transform step
The issue has been identified and a fix is being implemented.
A fix has been implemented, any failing steps should succeed on next run.
The Pull From Excel step, if you build a new integration, is broken since Tuesday afternoon, 2026-06-23 4:30pm Pacific Time (2026-06-23 23:30 UTC) We are working on a fix and will have it deployed soon.
This incident has been resolved.
We're currently investigating reports of visualizations not loading, or taking longer than expected to load, within Parabola. The issue appears to be intermittent and does not affect all visualizations or all users.
The issue with visualizations has been identified and a fix is being developed
This incident, in which visualizations were not loading or taking longer than expected to load, has been resolved. The issue was occurring for some customers from 2026-06-05 through 2026-06-10. We have solved the underlying cause and are following up with more to protect going forward.
From 13:24 to 13:32 UTC 2026-06-09, a small number of offline/scheduled runs failed, and some flow content saves may not have synced to the editor as expected. This was due to a brief disruption in a third-party service; the underlying service has fully recovered, and our systems have been stable since 13:32 UTC with no recurrence. If you ran a flow during this window and are unsure whether it completed, we recommend checking the flow's Run History and re-running the flow is necessary.
We have detected and identified errors in chatting with the assistive chat sidebar Prowork 2026-06-02 20:20-21:10 UTC. They are now resolved; users may resume conversations
We're currently investigating reports of issues with sending emails from Parabola. We're actively looking into the cause and will provide updates as we learn more.
We are continuing to investigate this issue.
This incident has been resolved. Email sending through Parabola has been fully restored, and flows that send email are operating normally. Earlier today, a subset of outbound emails failed to send. We identified the cause, took corrective action, and confirmed that delivery is back to normal. We're still working to identify and resend emails that were queued or failed during the affected window. We'll follow up with impacted customers directly as we complete this cleanup.
From 2026-05-21 20:37 - 20:45 UTC, the Parabola application was unavailable and flow runs were failing. During that time, webhook flow triggers were lost. Flows can now be retried. We're continuing to monitor to confirm stability before marking this incident as resolved. If you're continuing to see issues with your flows, please reach out to [email protected].
This incident has been stabilized and is resolved.
An outage at one of our underlying providers caused failures on Custom Transforms and Prowork steps, from 2026-05-01 16:19-16:38 UTC. The issue has been fixed and we continue to monitor.
We are currently investigating a situation where the chat assistant and custom transforms are not working, as of 2026-04-23 02:20 UTC
This incident has been resolved. From 2026-04-22 23:55 UTC to 2026-04-23 02:59 UTC, users were unable to build flows using the assistive chat sidebar From 2026-04-22 23:55 UTC to 2026-04-23 03:28 UTC, flow runs were failing on custom transforms, AI transforms, and some document parsing From 2026-04-23 04:00 UTC to 2026-04-23 19:20 UTC, some flow runs failed on custom transform steps, but succeed if retried. Customers with flows that failed during that window should go ahead and re-run their flows. From 2026-04-23 19:23 UTC to 2026-04-23 19:57 UTC, users were unable to build flows using the assistive chat sidebar and flow runs were failing on custom transforms, AI transforms, and some document parsing The root-cause was a misconfiguration of our LLM provider. That has been fixed -- we are reviewing to make it more robust.
An issue at our underlying AI provider is causing increased errors in some Custom Transform and Email file-parsing steps.
This incident has been resolved.
We are investigating reports of increased failures in CSV/Excel parsing steps
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Microsoft integrations have been failing since 2026-02-03 16:00 UTC -- we have identified the cause and are working to resolve it
This incident has been resolved. Integrations with Microsoft Excel, Sharepoint, and Dynamics were failing 2026-02-03 16:00 UTC - 2026-02-04 16:19 UTC
