Skip to navigation

Changelog

September 30, 2026

v2.3.2 — Remix actions run in request order

Remix actions now run one at a time in the order you list them, whether you send them on a workflow start (remixActions) or through POST /v1/projects/{projectId}/remix. Each action applies to the project as the previous action left it.

Changed

  • Remix action ordering: Actions no longer run in parallel. Each one starts after the previous one finishes, so total time is the sum of every action’s time. List setup edits such as RESIZE_PROJECT before media actions such as CONVERT_IMAGES_TO_VIDEOS.
  • Remix action failures: When an action fails, every action listed after it is reported as failed without running. Actions that already succeeded stay applied. Follow each action’s status with GET /v1/projects/{projectId}/remix-actions.