55 Parabola incidents · noviembre de 2019 — official updates, affected components, duration and resolution details.
Hemos identificado la lentitud en la finalización de los chats Prowork y seguimos investigando el impacto de los proveedores upstream en nuestro servicio.
Este incidente se ha resuelto
Traducido automáticamente desde la actualización oficial del incidente.
Hemos identificado la lentitud en la finalización del chat de Prowork y seguimos investigando
Los chats de prowork están funcionando normalmente
Traducido automáticamente desde la actualización oficial del incidente.
Estamos investigando informes de la lentitud del chat Prowork.
Hemos identificado la lentitud del chat Prowork y estamos buscando cambios para solucionarlo.
A fix has been deployed as of 2026-08-03 17:40 UTC (1:40pm EDT; 10:40am PDT) - estamos monitoreando para asegurar que los chats de prowork continúan mejorando.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
El equipo está trabajando en una resolución
El chat Prowork se está recuperando.
Cuestión resuelta
Traducido automáticamente desde la actualización oficial del incidente.
El chat Prowork no es sensible para muchos usuarios. El incidente está siendo investigado.
El chat de prowork ha sido poco responsable para muchos usuarios a partir de 2026-07-29 15:58 UTC. Al 2026-07-29 17:29 UTC, hemos mitigado la cuestión pero seguimos monitoreando para una resolución estable y plena.
El chat de prowork no fue responsable para muchos usuarios de 2026-07-29 15:58-17:29 UTC. Hemos mitigado y resuelto el problema, y continuaremos una causa de raíz retrospectiva para mejorar la estabilidad futura.
Traducido automáticamente desde la actualización oficial del incidente.
Estamos investigando informes de problemas con el paso de transformación personalizada
Se ha determinado la cuestión y se está aplicando una solución.
Se ha aplicado una solución, cualquier medida de fracaso debe tener éxito a la próxima carrera.
Traducido automáticamente desde la actualización oficial del incidente.
El paso Pull From Excel, si construyes una nueva integración, se rompe desde la tarde del martes 2026-06-23 4:30pm Pacific Time (2026-06-23 23:30 UTC) Estamos trabajando en una solución y lo tendremos desplegado pronto.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
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.