docs(automation): document the time-relative trigger (#1874)#3241
Merged
Conversation
Follow-up to the merged #1874 feature. Adds the declarative time-relative trigger to the two hand-written surfaces authors consult (the auto-generated reference and the trigger-schedule README already landed with the feature): - skills/objectstack-automation/SKILL.md — a "Time-relative triggers" section under Triggers, framed as the declarative replacement for the fragile date-equality-on-record-change anti-pattern (flows are heavily AI-authored, so this is where an author reaches for the wrong pattern). Cross-linked from the schedule flow-type row. - content/docs/automation/flows.mdx — a "Time-relative flow" example right after the hand-rolled scheduled get_record example it replaces. Doc gates verified locally: check:doc-authoring, check:skill-docs, check:docs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AHzW68suiFuu6GdJyea8U4
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
os-zhuang
marked this pull request as ready for review
July 18, 2026 16:32
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.
What & why
Follow-up to the merged #1874 feature (PR #3230). The feature landed with its auto-generated reference (
content/docs/references/automation/time-relative-trigger.mdx) and the trigger-schedule README section, but the two hand-written surfaces authors actually consult still described only record / schedule triggers. This adds the time-relative trigger to both.Changes
skills/objectstack-automation/SKILL.md— a Time-relative triggers section under "Triggers — Event-Driven Automation", framed explicitly as the declarative replacement for the fragile date-equality-on-record-change anti-pattern (end_date == daysFromNow(60)). This is the highest-value surface: flows are heavily AI-authored, and this skill is where an author reaches for the pattern in the first place. Also cross-links thescheduleflow-type row.content/docs/automation/flows.mdx— a Time-relative flow example placed right after the hand-rolled "Scheduled flow" (get_record+ notify) example it supersedes, with a note onoffsetDaysvswithinDaysand the requiredtriggers+jobcapabilities.Both frame the same guidance: prefer the declarative
config.timeRelativesweep (evaluated daily, fans out per record) over arecord_changeflow gated on date-equality (which only fires if the record is edited on the exact threshold day).Testing
Doc gates verified locally:
check:doc-authoring(200 files clean),check:skill-docs(in sync — body edit doesn't touch generated frontmatter),check:docs(references still in sync). No code changes, so no changeset.🤖 Generated with Claude Code
Generated by Claude Code