docs: document sandbox mode and skip delays for the workflow test runner

[cjbell]

Description

Documents two new settings for the workflow test runner:

• Sandbox mode — when enabled, all messages sent from the workflow are forced to send in sandbox mode, generating and previewing messages without delivering them to the underlying providers.
• Skip delays — when enabled, all delay steps in the workflow are force skipped, so the run executes straight through without waiting.

Both settings are also documented on the trigger API page via the settings.sandbox_mode and settings.skip_delay properties, which is useful when testing workflows programmatically.

Changes:

• content/send-notifications/testing-workflows.mdx — adds a "Test run settings" section.
• content/send-notifications/triggering-workflows/api.mdx — adds settings to the trigger payload table and a "Controlling trigger behavior with settings" section.

Note: settings.skip_delay is not yet present in the OpenAPI spec on main (only sandbox_mode is), so it won't render in the auto-generated API reference until the spec catches up.

Tasks

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 26, 2026 10:11pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c9e8dd3. Configure here.}

[cursor]

Risk LOW: Documents sandbox mode and skip delays settings for the workflow test runner across two existing MDX pages.

Reasons

• Only two .mdx content files are modified — no code, components, or configuration changes.
• Small, additive-only diff (32 additions, 0 deletions) well under the 50-line threshold.
• Both files live in the same documentation section (content/send-notifications/), so no cross-section risk.
• No new pages added — both files are modifications to existing docs.
• No sidebar, OpenAPI spec, or image changes.

Notes

• Reviewers may want to verify the anchor link #controlling-trigger-behavior-with-settings renders correctly from the cross-reference in testing-workflows.mdx.
• The PR description notes that settings.skip_delay is not yet in the OpenAPI spec on main, so the auto-generated API reference won't reflect it until the spec catches up — worth confirming that doesn't cause confusion for readers.

  

_{Sent by Cursor Automation: Docs PR classifier}

[rachael-t]

Wondering if we should update the title? Unclear if the settings object might expand use cases in the future, but for now, since it's just scoped to testing I think we should make that more clear? Open to suggestions on this though!

Suggested change

	## Controlling trigger behavior with settings
	## Testing workflow triggers

[rachael-t]

Should we move this to after the source event paragraph and before the callout? It feels a bit disjointed being inserted into this existing section (curious what others think)