fix(kno-15032): document object recipient workflow runs - #1652
Open
scotidodson wants to merge 1 commit into
Open
fix(kno-15032): document object recipient workflow runs#1652scotidodson wants to merge 1 commit into
scotidodson wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
scotidodson
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk MEDIUM: Clarifies that object workflow triggers generate a run for the object itself in addition to fan-out to subscribers.
Reasons
- Changes span multiple documentation sections (
content/concepts/andcontent/send-notifications/) - Only MDX content files are modified — no components, layouts, lib, styles, or build config
- Small diff (22 additions, 9 deletions across 3 files)
- No new pages, sidebar navigation changes, or OpenAPI spec updates
- Author
scotidodsonis a known repository contributor
Notes
- Verify the new "Object workflow runs" section and updated fan-out language are technically accurate
- Check cross-links between objects, subscriptions, and trigger API pages resolve correctly
- Confirm the new FAQ on skipping object runs aligns with current product behavior and support guidance
- Review step condition examples (
__typename,collection) for accuracy
Sent by Cursor Automation: Docs PR classifier
cellomatt
approved these changes
Aug 28, 2026
| </Accordion> | ||
| <Accordion title="Can I notify both the object AND the subscribers of the object?"> | ||
| Yes, by default when you trigger a workflow for an object that has | ||
| Yes. By default when you trigger a workflow for an object that has |
Member
There was a problem hiding this comment.
Suggested change
| Yes. By default when you trigger a workflow for an object that has | |
| Yes. When you trigger a workflow for an object that has |
| /> | ||
|
|
||
| ## Referencing object data in templates | ||
| ## Object workflow runs |
Member
There was a problem hiding this comment.
I might place this section above the subscribers heading, because it's relevant whether or not an object has subscribers, but not a big deal either way.
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.
KNO-15032: Clarify that object triggers generate a workflow run for the object itself
Summary
Changes
content/concepts/objects.mdx— object subscribers intro now covers the object run; added an "Object workflow runs" section; shortened "Referencing object data in templates" to "Referencing object data".content/concepts/subscriptions.mdx— renamed the trigger section, corrected the "How subscriptions work" fan-out sentence, updated one FAQ accordion and added another on skipping the object run.content/send-notifications/triggering-workflows/api.mdx— trigger FAQ now includes the object run.