Continuous workflow runs steps at same time instead of step by step?
I have this problem where I defined a workflow with 4 steps in a continuous schedule, but at least two steps run simultaneously.
Not only in this screen, but I can see live in the Job log due timestamps on that they are actually running at same time. 
d6136a1c-98c8-494c-a946-06d21467b245.png
Hello @denistiri
Thank you for reporting this.
From the screenshot, I can see that multiple child jobs from the workflow appear to be running at the same time. Before determining whether this is expected workflow behavior or something we should reproduce, I would like to confirm a few details:
• What exact PowerShell Universal version and build are you running?
• Are the four workflow steps connected as a single sequential chain, for example Step 1 -> Step 2 -> Step 3 -> Step 4?
• Could you share a sanitized screenshot of the complete Workflow Designer showing the steps and their connections?
• What interval is configured for the continuous schedule?
• Does this happen on every workflow execution or only intermittently?
It would also be useful to confirm whether the simultaneously running jobs belong to the same parent workflow execution.
Once we have those details, we can determine whether a controlled reproduction is needed.
Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.
Best regards,
Ruben Tapia
@denistiri @rubentapia I'd also like to ask how long your individual steps take and what version you are on. The reason is that we had a workflow activity issue where if a job ran for over 30 seconds, the workflow engine would internally timeout and incorrectly move to the next step. This has since been resolved.
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions