Choose when your workflow waits for a proposal to finish ⏸️
Shared by Mitt • A new Wait for build toggle on the Start Proposal step lets you hold for the full build or continue downstream the moment it kicks off.
Some workflow steps need a finished proposal to act on; others just need the build to kick off. With the new Wait for build toggle on the Start Proposal step, you decide which — keep waiting for the full build, or continue downstream the moment it starts.
What's New
The Start Proposal step now has a Wait for build toggle: "Wait for proposal to finish building." Leave it on to hold the workflow until the proposal is fully built, or switch it off to let downstream steps run as soon as the build begins.
How It Works
- Open any workflow and click into a Start Proposal step
- ⏸️ Toggle "Wait for proposal to finish building" on (the default) to keep waiting — downstream steps run once the proposal is done and can read and act on it
- ▶️ Toggle it off for fire-and-forget — downstream steps run immediately after the build starts, without waiting on the finished proposal
Why It Matters
Proposal builds take a few minutes. If your next step just sends a "build started" notification, there's no reason to wait — and now it doesn't have to. Because each step is timed against the work it actually does, your run history finally shows where the time really goes, so you can spot what's actually slowing a run down instead of guessing.
Get Started
Open a workflow, click your Start Proposal step, and find the "Wait for proposal to finish building" toggle. Existing workflows keep waiting by default — nothing changes unless you switch it off. New to automations? Head to Workflows to build one.
Happy building! 🚀