Parabola driftsforstyrrelser

1. 8. september 2026 kl. 19.27 UTCinvestigating

   Vi undersøger et problem blokerer bruger- login og nogle prowork chats, siden 2026-09- 08 18: 10 UTC

2. 8. september 2026 kl. 19.56 UTCmonitoring

   Vi har mindsket problemet fra 2026 til 09- 08 19: 41 UTC og overvåger nu

3. 8. september 2026 kl. 20.51 UTCresolved

   Denne hændelse er nu løst: Parabola brugere stod over for problemer visning og bygning strømme, fra 2026- 09- 08 2: 10-3: 41pm EDT (11: 10am- 12: 41pm PDT). Vi har mindsket problemet fuldt ud og overvåger for at sikre, at fremtidige problemer ikke gentager sig. For de brugere, der var ved at bygge, chatte med Prowork, eller kicking off strømme manuelt, et lille antal brugere havde individuelle handlinger eller chats til at opbygge en flow fiasko. Disse brugere så en fiasko i Parabola web-program og bør fortsætte bygningen For de brugere, der stod over for spørgsmål som at være logget ud, eller webpage- visninger for strømme, der ikke dukker op, spørgsmålene var intermitterende i dette vindue, og brugerne kan fortsætte med deres arbejde.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. september 2026 kl. 15.43 UTCidentified

   Vi har identificeret langsommelighed i færdiggørelsen af Prowork chat og fortsætter med at undersøge virkningen fra opstrøms udbydere på vores service.

2. 1. september 2026 kl. 20.31 UTCresolved

   Denne hændelse er blevet løst

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 18.10 UTCidentified

   Vi har identificeret langsommelighed i Prowork chat afslutning og fortsætter med at undersøge

2. 31. august 2026 kl. 21.32 UTCresolved

   Prowork chats kører nu normalt

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. august 2026 kl. 15.08 UTCinvestigating

   Vi undersøger rapporter om Prowork chat langsommelighed.

2. 3. august 2026 kl. 16.41 UTCidentified

   Vi har identificeret Prowork chat langsommelighed og forfølger ændringer til at løse det.

3. 3. august 2026 kl. 18.13 UTCmonitoring

   Et fix er blevet indsat fra 2026- 08- 03 17: 40 UTC (1: 40pm EDT; 10: 40am PDT) -- vi overvåger at prowork chats fortsat forbedres.

4. 3. august 2026 kl. 18.25 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juli 2026 kl. 16.29 UTCidentified

   Team arbejder på en resolution

2. 29. juli 2026 kl. 16.35 UTCmonitoring

   Prowork chat er ved at komme sig.

3. 29. juli 2026 kl. 16.43 UTCresolved

   Emne løst

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juli 2026 kl. 17.15 UTCidentified

   Prowork chat er ikke lydhør for mange brugere. Hændelsen er under efterforskning.

2. 29. juli 2026 kl. 17.29 UTCmonitoring

   Prowork chat har været uresponsive for mange brugere, der starter ved 2026- 07- 29 15: 58 UTC. Fra 2026-07- 29 17: 29 UTC, vi har afbødet spørgsmålet, men fortsætter med at overvåge for en stabil, fuld opløsning.

3. 29. juli 2026 kl. 22.20 UTCresolved

   Prowork chat var ikke lydhør for mange brugere fra 2026- 07- 29 15: 58- 17: 29 UTC. Vi har afbødet og løst problemet og vil fortsætte med en bagudrettet årsag til at forbedre den fremtidige stabilitet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. juli 2026 kl. 13.34 UTCinvestigating

   Vi undersøger rapporter om problemer med Custom Transform trin

2. 16. juli 2026 kl. 14.04 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 16. juli 2026 kl. 15.53 UTCresolved

   Et fix er blevet gennemført, alle fejltrin skal lykkes på næste løb.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juni 2026 kl. 00.16 UTCidentified

   Trækket fra Excel, hvis du bygger en ny integration, er brudt siden tirsdag eftermiddag, 2026- 06- 23 4: 30 pm Pacific Time (2026- 06- 23: 30 UTC) Vi arbejder på et fix og vil få det indsat snart.

2. 24. juni 2026 kl. 01.04 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juni 2026 kl. 17.31 UTCinvestigating

   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.

2. 10. juni 2026 kl. 17.40 UTCidentified

   The issue with visualizations has been identified and a fix is being developed

3. 10. juni 2026 kl. 22.52 UTCresolved

   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.

1. 9. juni 2026 kl. 15.58 UTCresolved

   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.

1. 2. juni 2026 kl. 23.08 UTCresolved

   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

1. 1. juni 2026 kl. 14.53 UTCinvestigating

   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.

2. 1. juni 2026 kl. 15.13 UTCinvestigating

   We are continuing to investigate this issue.

3. 1. juni 2026 kl. 17.33 UTCresolved

   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.

1. 21. maj 2026 kl. 20.52 UTCmonitoring

   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].

2. 21. maj 2026 kl. 21.00 UTCresolved

   This incident has been stabilized and is resolved.

1. 1. maj 2026 kl. 17.05 UTCresolved

   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.

1. 23. april 2026 kl. 02.35 UTCinvestigating

   We are currently investigating a situation where the chat assistant and custom transforms are not working, as of 2026-04-23 02:20 UTC

2. 23. april 2026 kl. 03.03 UTCresolved

   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.

1. 13. april 2026 kl. 20.07 UTCmonitoring

   An issue at our underlying AI provider is causing increased errors in some Custom Transform and Email file-parsing steps.

2. 14. april 2026 kl. 04.54 UTCresolved

   This incident has been resolved.

1. 11. marts 2026 kl. 16.00 UTCinvestigating

   We are investigating reports of increased failures in CSV/Excel parsing steps

2. 11. marts 2026 kl. 16.18 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11. marts 2026 kl. 17.10 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11. marts 2026 kl. 17.57 UTCresolved

   This incident has been resolved.

1. 4. februar 2026 kl. 15.08 UTCidentified

   Microsoft integrations have been failing since 2026-02-03 16:00 UTC -- we have identified the cause and are working to resolve it

2. 4. februar 2026 kl. 16.19 UTCresolved

   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

1. 8. januar 2026 kl. 20.48 UTCidentified

   Custom Transforms are failing to execute; we are investigating and have identified the root issue.

2. 8. januar 2026 kl. 21.02 UTCmonitoring

   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

3. 8. januar 2026 kl. 21.14 UTCresolved

   This incident has been fully resolved. The Custom Transform step was broken from 2026-01-08 19:22 - 21:01 UTC

1. 15. december 2025 kl. 22.15 UTCidentified

   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.

2. 15. december 2025 kl. 22.15 UTCidentified

   We are continuing to work on a fix for this issue.

3. 15. december 2025 kl. 22.55 UTCmonitoring

   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

4. 16. december 2025 kl. 01.25 UTCresolved

   This incident has been resolved.