Parabola 장애 기록

1. 2026년 9월 1일 PM 3:43 UTCidentified

   우리는 Prowork 채팅 완료에 느리게 식별하고 우리의 서비스에 업스트림 제공 업체의 영향을 조사하기 위해 계속됩니다.

2. 2026년 9월 1일 PM 8:31 UTCresolved

   이 사건은 해결되었습니다

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 31일 PM 6:10 UTCidentified

   우리는 Prowork 채팅 완료에서 느리게 식별하고 조사 계속됩니다

2. 2026년 8월 31일 PM 9:32 UTCresolved

   Prowork 채팅은 일반적으로 실행됩니다

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 3일 PM 3:08 UTCinvestigating

   Prowork 채팅 느린의 조사 보고서입니다.

2. 2026년 8월 3일 PM 4:41 UTCidentified

   우리는 Prowork 채팅 느리게 식별하고 수정하는 변경 사항입니다.

3. 2026년 8월 3일 PM 6:13 UTCmonitoring

   수정은 2026-08-03 17:40 UTC (1:40pm EDT; 10:40am PDT)로 배포되었습니다 -- 우리는 Prowork 채팅을 계속 개선하기 위해 모니터링하고 있습니다.

4. 2026년 8월 3일 PM 6:25 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 29일 PM 4:29 UTCidentified

   팀은 해결책에 일하고 있습니다

2. 2026년 7월 29일 PM 4:35 UTCmonitoring

   Prowork 채팅은 복구입니다.

3. 2026년 7월 29일 PM 4:43 UTCresolved

   문제 해결

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 29일 PM 5:15 UTCidentified

   Prowork 채팅은 많은 사용자에게 응답하지 않습니다. 사건은 조사의 밑에 있습니다.

2. 2026년 7월 29일 PM 5:29 UTCmonitoring

   Prowork 채팅은 2026-07-29 15:58 UTC에서 시작하는 많은 사용자에게 응답하지 않았습니다. 2026-07-29 17:29 UTC로, 우리는 문제가 모방했지만 안정적이고 풀 해상도를 모니터링하는 것을 계속했습니다.

3. 2026년 7월 29일 PM 10:20 UTCresolved

   Prowork 채팅은 2026-07-29 15:58-17:29 UTC에서 많은 사용자에 대해 응답하지 않았습니다. 우리는 mitigated와 문제점을 해결하고, 미래 안정성을 개량하기 위하여 개조한 뿌리 때문에 계속할 것입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 PM 1:34 UTCinvestigating

   우리는 사용자 정의 Transform 단계와 문제의 조사 보고서

2. 2026년 7월 16일 PM 2:04 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 16일 PM 3:53 UTCresolved

   수정이 시행되었습니다. 실패한 단계는 다음 실행에 성공해야 합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 24일 AM 12:16 UTCidentified

   Excel 단계에서 새로운 통합을 구축하면 화요일 오후 2026-06-23 4:30pm Pacific Time (2026-06-23 23:30 UTC) 이후 부서집니다. 우리는 해결에 노력하고 곧 배포 될 것입니다.

2. 2026년 6월 24일 AM 1:04 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 10일 PM 5: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. 2026년 6월 10일 PM 5:40 UTCidentified

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

3. 2026년 6월 10일 PM 10: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. 2026년 6월 9일 PM 3: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. 2026년 6월 2일 PM 11: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. 2026년 6월 1일 PM 2: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. 2026년 6월 1일 PM 3:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 6월 1일 PM 5: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. 2026년 5월 21일 PM 8: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. 2026년 5월 21일 PM 9:00 UTCresolved

   This incident has been stabilized and is resolved.

1. 2026년 5월 1일 PM 5: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. 2026년 4월 23일 AM 2: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. 2026년 4월 23일 AM 3: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. 2026년 4월 13일 PM 8:07 UTCmonitoring

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

2. 2026년 4월 14일 AM 4:54 UTCresolved

   This incident has been resolved.

1. 2026년 3월 11일 PM 4:00 UTCinvestigating

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

2. 2026년 3월 11일 PM 4:18 UTCidentified

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

3. 2026년 3월 11일 PM 5:10 UTCmonitoring

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

4. 2026년 3월 11일 PM 5:57 UTCresolved

   This incident has been resolved.

1. 2026년 2월 4일 PM 3: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. 2026년 2월 4일 PM 4: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. 2026년 1월 8일 PM 8:48 UTCidentified

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

2. 2026년 1월 8일 PM 9: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. 2026년 1월 8일 PM 9:14 UTCresolved

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

1. 2025년 12월 15일 PM 10: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. 2025년 12월 15일 PM 10:15 UTCidentified

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

3. 2025년 12월 15일 PM 10: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. 2025년 12월 16일 AM 1:25 UTCresolved

   This incident has been resolved.

1. 2025년 11월 14일 PM 3:56 UTCidentified

   We are addressing reports of delayed runs and slower steps.

2. 2025년 11월 14일 PM 4:07 UTCresolved

   We have implemented a fix and are seeing step and flow run times return to normal levels.