docs: add Schedule trigger page for cron-scheduled agent runs - #155
Merged
Conversation
👷 Deploy request for redpanda-agentic-data-plane pending review.Visit the deploys page to approve it
|
alenkacz
force-pushed
the
docs/schedule-trigger
branch
from
July 27, 2026 05:14
9bb397a to
401e143
Compare
Document the Schedule trigger, which runs a deployed agent automatically on a recurring cron schedule in a chosen timezone. Covers adding the trigger with a preset or a five-field cron expression, the 15-minute minimum interval, the required timezone, the input prompt, run-as-creator semantics, one-shot behavior, run outcomes, and troubleshooting. Also generalize the triggers overview to cover both channel and schedule triggers, and add the page to the nav. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
alenkacz
force-pushed
the
docs/schedule-trigger
branch
from
July 27, 2026 05:23
401e143 to
8d966b4
Compare
…title - Retitle the triggers overview to "Trigger Agents" so it covers both channel and schedule triggers - Remove the em dash from the cron field reference - Unbold field names, section labels, preset values, and run-status legends; keep bold on click targets only - Reword the preset selection step Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Capitalize the Details, Input, and Schedule section references so they match the form section names in the UI, while keeping field values lowercase. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
micheleRP
approved these changes
Jul 28, 2026
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
Adds documentation for the Schedule trigger, which runs a deployed agent automatically on a recurring cron schedule in a chosen timezone.
connect:triggers/schedule.adoc— add a schedule trigger with a preset or a five-field cron expression, the 15-minute minimum interval, the required timezone (IANA, DST-aware), the input prompt, run-as-creator semantics, one-shot behavior, run outcomes (Succeeded, Failed, Missed, Skipped), managing/editing, and troubleshooting.connect:triggers/overview.adoc— generalized so the overview covers both channel triggers (Microsoft Teams) and schedule triggers, with a note on how schedule status is reported.nav.adoc— adds the new page under Triggers.Documented as GA (no beta badge), consistent with the Microsoft Teams trigger page.
How it was verified
origin/main: theCronTrigger/TriggerRunproto, theapps/adp-uitrigger components, and the in-adp-apischeduler.Notes for reviewers