Update exec_mode values in data warehouse sync reference - #1614
Merged
Conversation
- Add missing exec_mode values: audience, rehearse_integration, workflow_step_trigger, broadcast_trigger, rehearse_broadcast, guide - Remove incorrect value: rehearse_step (filtered out of export) - Update descriptions to be more accurate and consistent - Now lists all 10 user-facing exec_mode values that appear in fct_messages_export Co-authored-by: Rachael Thomas <rachael-t@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rachael-t
marked this pull request as ready for review
August 19, 2026 18:05
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk LOW: Updates the exec_mode column reference in the data warehouse sync docs to match the 10 user-facing values exported in models.fct_messages_export.
Reasons
- Only 1 file changed:
content/integrations/extensions/data-sync.mdx(content-only MDX edit) - Small diff: 20 additions, 5 deletions (25 total lines changed)
- No code, config, sidebar, or OpenAPI spec changes
- No new pages, images, or cross-section edits
- Author
rachael-tis a known team member
Notes
- Verify the 10 listed
exec_modevalues (audience,trigger,rehearse,integration,rehearse_integration,scheduled,workflow_step_trigger,broadcast_trigger,rehearse_broadcast,guide) match the current export schema and that removingrehearse_stepis correct for customer-facing data - Confirm updated descriptions (e.g. "real execution of a workflow from the API") align with product terminology used elsewhere in the docs
Sent by Cursor Automation: Docs PR classifier
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the
exec_modecolumn reference in the data warehouse sync documentation to reflect the actual values present in the customer-facingmodels.fct_messages_exporttable.What changed:
exec_modevalues:audience,rehearse_integration,workflow_step_trigger,broadcast_trigger,rehearse_broadcast, andguiderehearse_stepvalue (filtered out of the export)Why:
The documentation was ~2 years old and no longer matched the data customers actually receive. The exported set corresponds to Knock's canonical "user-facing" exec modes, which includes 10 values (the full 12-value message enum minus
rehearse_stepandinternal).Todos
Tasks
KNO-14869
Linear Issue: KNO-14869
Screenshots
Before
After