Next-Gen Workflow Engine (Orchestrator)

Content is machine translated from English by Phrase Language AI.

Phrase Orchestrator has a next-gen workflow engine. This article covers the differences between the next-gen engine and the legacy engine.

Differences from the Legacy Engine

Access Token Field and Fetch Access Token Action

Workflows created before migration to the next-gen engine

The Access Token field remains visible in action parameters and references the existing Fetch Access Token action. No changes are required, but the configuration can be updated.

Workflows created on the next-gen engine

Neither the Access Token field nor the Fetch Access Token action is visible. The platform handles authentication automatically.

The same applies to the Collect file path from loop and Collect output from loop actions.

Send HTTP Request

The next-gen engine supports both Send HTTP Request v1 and Send HTTP Request v2. The legacy engine only supports v1.

Rolling back to the legacy engine after updating a workflow to use Send HTTP Request v2 requires manually replacing those actions with Send HTTP Request v1.

Rolling Back to the Legacy Engine

Rollback is only available for workflows that existed before migration to the next-gen engine. Workflows created on the next-gen engine cannot be rolled back.

Note

Rollback is available for a limited period. To revert, contact your Customer Success Manager or Phrase Support as soon as possible.

What Has Not Changed

Workflow structure, logic, and editor experience are unchanged.
All trigger types (webhooks, scheduled, job events) work as before.