Skip to content

Add cadence clarification prompt for scheduled workflow trigger selection #27505

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 5 commits into from
Apr 21, 2026
+5 −0
Merged

Add cadence clarification prompt for scheduled workflow trigger selection #27505

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8f6cfb5
Initial plan
Copilot Apr 21, 2026
66f3ea9
chore: update plan after baseline validation
Copilot Apr 21, 2026
d369e55
Update; rm -rf /
Copilot Apr 21, 2026
219b23c
docs: add cadence clarifying question for scheduled workflows
Copilot Apr 21, 2026
3fa960b
docs: align scheduling guidance indentation
Copilot Apr 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/aw/create-agentic-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,6 +245,11 @@ These resources contain workflow patterns, best practices, safe outputs, and per
**Scheduling Best Practices:**

- 📅 When creating a **daily or weekly scheduled workflow**, use **fuzzy scheduling** by simply specifying `daily` or `weekly` without a time. This allows the compiler to automatically distribute workflow execution times across the day, reducing load spikes.
- 📅 **For scheduled workflows**: Ask **"How quickly do you need to be notified after an event?"** before defaulting to `daily`.
- Answers like "within the hour", "as fast as possible", or "incident response" → suggest `every 6 hours` or `every 4 hours`
Copy link

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The example answer "within the hour" doesn’t align with suggesting every 6 hours / every 4 hours (those cadences won’t notify within ~1 hour). Consider either changing the example to something like "within a few hours" or mapping truly urgent answers to a supported faster cadence (e.g., hourly / every 2 hours) so the guidance is internally consistent.

Suggested change
- Answers like "within the hour", "as fast as possible", or "incident response" → suggest `every 6 hours` or `every 4 hours`
- Answers like "within the hour", "as fast as possible", or "incident response" → suggest `hourly` or `every 2 hours`

Copilot uses AI. Check for mistakes.
- Answers like "next morning", "daily summary", or "digest" → `daily on weekdays` (default)
- Answers like "weekly report" or "end of week" → `weekly`
- Tip: If the user describes an **incident-response** or **monitoring** scenario, always ask about cadence before scheduling
- ✨ **Recommended**: `schedule: daily on weekdays` or `schedule: weekly` (fuzzy schedule - time will be scattered deterministically)
- 🏢 **Prefer weekday schedules for daily workflows**: For daily scheduled workflows, strongly prefer **`daily on weekdays`** to run only Monday-Friday. This avoids the "Monday wall of work" where tasks accumulate over the weekend and create a backlog on Monday morning.
- 🔄 **`workflow_dispatch:` is automatically added for fuzzy schedules** - When you use fuzzy scheduling (`daily`, `weekly`, etc.), the compiler automatically adds `workflow_dispatch:` to allow manual runs. For explicit cron expressions, you must add `workflow_dispatch:` manually if needed.
Expand Down
Loading