Phrase incident

Degraded Performance of Phrase Orchestrator (EU) Workflow Engine component between August 25, 2025 and September 1, 2025

Minor Resolved View vendor source →

Phrase experienced a minor incident on August 26, 2025 affecting Legacy Workflow Engine, lasting 6d 15h. The incident has been resolved; the full update timeline is below.

Started
Aug 26, 2025, 09:03 PM UTC
Resolved
Sep 02, 2025, 12:57 PM UTC
Duration
6d 15h
Detected by Pingoru
Aug 26, 2025, 09:03 PM UTC

Affected components

Legacy Workflow Engine

Update timeline

  1. investigating Aug 26, 2025, 09:03 PM UTC

    Users might be experiencing delays in the execution of Orchestrator workflows hosted in the EU data center. Our engineers are investigating the situation.

  2. investigating Aug 27, 2025, 03:44 PM UTC

    Users may still experience occasional delays in Orchestrator workflow executions. We are continuing to investigate this issue.

  3. identified Aug 28, 2025, 03:43 PM UTC

    We have identified the issue causing intermittent delays in workflow executions and are working on optimizing the execution queue. While performance has been relatively stable, some users may still experience occasional delays in Orchestrator workflow executions. Our team continues to closely monitor the situation. If you encounter significant delays, please reach out to Phrase Technical Support.

  4. monitoring Aug 29, 2025, 11:55 AM UTC

    Workflow executions are operating as expected, and no further delay spikes have been observed in the past 24 hours. We will continue to monitor the situation closely.

  5. monitoring Sep 01, 2025, 01:32 PM UTC

    We have implemented scalability improvements designed to eliminate further delays in workflow executions. Performance is stable, and we will continue to monitor the situation closely.

  6. resolved Sep 02, 2025, 12:57 PM UTC

    Since implementing scalability improvements, workflow executions have remained stable and performance is back to normal. These changes also make the system more robust in handling future workload spikes.