[juanmleng]

Pull Request Description

What and why?

Documents the new Wait for Completion option on the Run Workflow step, which pauses a workflow until the workflow it started has finished, and how to act on the outcome with a Condition Branch placed after the step, including looping back to an earlier phase. Updates the step's guide entry and training summary, and notes where a run's Waiting For and Started By details appear.

The step has no routing options of its own: a Condition Branch after the waiting step already checks the record once the other workflow finishes and can lead back to an earlier step, so the guide points to that instead of adding a second way to do the same thing.

Pages changed

Live pages as they are today, at the changed section (preview links to follow once validate deploys):

• Workflow step types → Run Workflow: new Wait for Completion content and the Condition Branch pattern
• Working with workflows → View all workflow executions: Waiting For and Started By in a run's details
• Training: Using ValidMind for risk management, workflow step types slide: Run Workflow summary
• Training: Organizational oversight and reporting, view workflow executions slide: shared with the guide page above; the slide version is unchanged

How to test

Render the affected pages: workflow-step-types.qmd, working-with-workflows.qmd, and the training pages using-validmind-for-risk-management.qmd and organizational-oversight-reporting.qmd. Preview links to follow once validate deploys.

What needs special review?

The recovery steps for a blocked workflow (Customer Admin, Step Detail panel), and the availability footnote.

Dependencies, breaking changes, and deployment notes

Publish with the platform release that adds these options; the setting is enabled per organization.

Release notes

Run Workflow steps can now wait for the workflow they start to finish before moving on, so one workflow can run each phase of a process in turn. Learn more

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

🤖 Generated with Claude Code

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview