55 Parabola incidents · novembre 2019 — official updates, affected components, duration and resolution details.
Nous avons identifié la lenteur dans l'achèvement du chat Prowork et continuons d'étudier l'impact des fournisseurs en amont sur notre service.
Cet incident a été résolu
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous avons identifié la lenteur dans l'achèvement du chat Prowork et continuons à enquêter
Les discussions sont maintenant en cours normalement
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons sur les rapports de la lenteur de discussion Prowork.
Nous avons identifié Prowork chat lentness et sont en train de poursuivre des changements pour le réparer.
Une correction a été déployée à partir de 2026-08-03 17:40 UTC (1:40h HAE; 10:40h HAE) -- nous surveillons pour assurer que les conversations prowork continuent à s'améliorer.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
L'équipe travaille sur une résolution
La conversation est en cours.
Problème résolu
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Le chat prowork n'est pas réceptif pour de nombreux utilisateurs. L'incident fait l'objet d'une enquête.
Le chat prowork n'a pas répondu pour de nombreux utilisateurs à partir de 2026-07-29 15:58 UTC. En date de 2026-07-29 17:29 UTC, nous avons atténué la question, mais continuons à surveiller pour une résolution stable et complète.
Le chat prowork n'a pas répondu pour de nombreux utilisateurs de 2026-07-29 15:58-17:29 UTC. Nous avons atténué et résolu le problème et nous continuerons à en faire une cause profonde rétrospective pour améliorer la stabilité future.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons sur les rapports de problèmes avec l'étape de la transformation personnalisée
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Une correction a été mise en place, toute étape défaillante devrait réussir à la prochaine étape.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
L'étape Pull From Excel, si vous construisez une nouvelle intégration, est cassée depuis mardi après-midi, 2026-06-23 16:30 heure du Pacifique (2026-06-23 23:30 UTC) Nous travaillons sur une solution et nous allons la déployer bientôt.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
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.
We are addressing reports of delayed runs and slower steps.
We have implemented a fix and are seeing step and flow run times return to normal levels.