On this page
Schedules
Ask for a follow-up or a recurring task in plain words or cron, and understand what survives a restart and what happens to late runs.
A schedule makes RevampKey come back to a task on its own. You describe when in plain words or with a cron expression, and the run happens in the same project, with the context it already has.
Say what and when
Write it the way you would tell a colleague, such as "every weekday at 9, check yesterday's bookings and flag anything odd" or "check back in 5 minutes and tell me if the deploy finished". A cron expression works too.
Check how it was read
The schedule shows when it will run and the next run time. If the timing is not what you meant, correct it before relying on it.
Choose how long it lasts
An Always schedule survives restarting the app. A This window follow-up ends when you close the window, and the app says so when it is created.
Review the result
When a run happens, what it found is posted back to you. Treat it like any other result: check it against the project before acting on it.
| Situation | What happens | Useful next action |
|---|---|---|
| The clocks change | A schedule for 9:00 stays at 9:00 local time. | No action is needed. |
| The app was closed when a run was due | The run happens once when the app launches and is marked as late. | Check the late marker when the result timing matters. |
| You close the window with a This window follow-up | The follow-up ends. | Use an Always schedule when the work should continue. |
| The agent is waiting on something slow | It can schedule its own check and come back. These are marked Agent. | Review or remove an agent-set follow-up like any other schedule. |
Continue learning
See the Schedules page for examples by role, or Projects, conversations, and tasks to see where scheduled work appears.
Report a documentation problem or contact the RevampKey team.