Announcement
This page is also available in Deutsch, Español, Français, Italiano, 日本語, and Português.
CloudFlow: Run independent actions in parallel with the new Parallel paths node
The new Parallel paths node lets you split a flow into independent paths, so unrelated tasks no longer share one sequence and a failure in one path doesn't disrupt the others.
FinOps and governance workflows often need to trigger several independent responses to the same event. For example, a cost anomaly might require notifying the FinOps team, creating a ticket for the resource owner, and recording the incident for later analysis. A policy violation might need to alert security, open a remediation task, and notify the relevant engineering team.
Previously, these actions had to be arranged in a single sequence, even when none depended on another. This made flows longer and harder to maintain, while a failure in one action could prevent unrelated follow-up work.
The new Parallel paths node lets you split a flow into 2–10 independent paths that receive the same input. Each path can handle a separate response, and a failure in one path does not stop the others. This makes it easier to build resilient cost-control, compliance, notification, and remediation workflows.
Parallel paths express independent work; they do not guarantee concurrent execution or execution order.
