How to use the Cron Expression Explainer.
Explain cron fields using the actual runtime's conventions. Calendar and timezone behavior are part of the schedule, not incidental settings.
Make the workflow fit your task.
Read each cron field using the stated scheduler's conventions and explain the combined schedule in ordinary language. Include timezone assumptions and check dates that expose weekday or month-boundary misunderstandings.
- What you provide
- Cron expression and runtime.
- What you get
- Human-readable schedule with edge cases.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Five-field Unix expression: 30 8 * * 1-5.
Completed example
Runs at 08:30 Monday through Friday in the scheduler's configured timezone.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does a cron expression always contain its timezone?
Often timezone is configured separately. Explain the runtime assumption rather than presenting an unqualified local time.
Why does the schedule run on more days than expected?
Check day-of-month and day-of-week interaction in the actual implementation. Field combinations can behave differently from a simple verbal guess.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑