56 Parabola incidents · 2019年11月 — official updates, affected components, duration and resolution details.
我们正在调查一个问题 阻断用户登录 和一些工作聊天, 从2026-09-08 18:10 UTC
我们从协调世界时2026-09-08 19:41开始缓解这一问题,目前正在监测
这一事件现已解决:帕拉博拉用户面临问题取景和建筑流量,从2026-09-08 2:10-3:41pm EDT(11:10am-12:41pm PDT)起. 我们已经完全缓解了这个问题,并且正在进行监测,以确保今后的问题不再出现。 对于正在建设、与Prowork聊天或手动启动流量的用户,少数用户有个人动作或聊天来构建流量故障。 这些用户看到Parabola网页应用程序出现故障,应继续建设 对于那些面临被登出或网页浏览流量未显示等问题的用户来说,这些问题在这个窗口中是断断续续的,用户可以继续工作.
自动翻译自官方事件更新。
我们已查明Prowork聊天完成缓慢,并正在继续调查上游供应商对我们服务的影响.
这件事已经解决了
自动翻译自官方事件更新。
我们发现Prowork聊天完成缓慢,正在继续调查
Prowork 聊天现在正常运行
自动翻译自官方事件更新。
我们正在调查关于Prowork聊天缓慢的报告.
我们已查明Prowork聊天缓慢,并正在寻求改变以纠正它.
截至2026-08-03 17:40 UTC (1:40pm EDT; 10:40am PDT) - 我们正在监测,以确保平面聊天继续改善.
这一事件已经得到解决.
自动翻译自官方事件更新。
团队正在拟订一项决议
Prowork聊天正在恢复.
问题已解决
自动翻译自官方事件更新。
Prowork聊天对许多用户没有反应. 事件正在调查中.
从协调世界时2026-07-29 15:58开始,Prowork聊天对许多用户一直没有响应. 截至2026-07-29 17:29 UTC,我们已经缓解了这个问题,但继续进行监测以稳定,全面解决.
Prowork聊天在协调世界时2026-07-29 15:58-17:29对许多用户没有响应. 我们已减轻并解决了这一问题,并将继续以追溯性根源来改善未来的稳定.
自动翻译自官方事件更新。
我们正用定制变换步骤调查一些问题
这一问题已经确定,一个解决办法正在实施之中.
已经执行了一项措施,任何失败的步骤都应在下一轮取得成功.
自动翻译自官方事件更新。
Pull From Excel阶梯,如果建造新的集成,则自太平洋时间(协调世界时2026-06-2323:30)周二下午起被打破. 我们正在寻找解决办法,并将很快部署.
这一事件已经得到解决.
自动翻译自官方事件更新。
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
Custom Transforms are failing to execute; we are investigating and have identified the root issue.
The fix has been deployed and the impact is over The Custom Transform step was broken from 2026-01-08 19:22 - 21:00 UTC
This incident has been fully resolved. The Custom Transform step was broken from 2026-01-08 19:22 - 21:01 UTC
There is an issue which is causing scheduled flow runs, triggered flow runs, and editing & saving flows to fail. Errors building and saving were 21:28 - 21:41 UTC 2025-12-15 . We are mitigating further impact on flow runs. Scheduled runs as of 21:28 UTC 2025-12-15 are delayed.
We are continuing to work on a fix for this issue.
A fix has been implemented and both flow building and flow runs should be fully functional. There were errors building and saving 21:28 - 21:41 UTC 2025-12-15 There were 400 Flows that have failed -- they had been scheduled for 21:28 - 22:25 UTC 2025-12-15
This incident has been resolved.