Pausing an AI employee during holidays without losing anything
When the office closes, an AI employee can skip holidays, pause until a date or keep working quietly. How to choose, and how to make sure it picks up cleanly when you return.
Part of the guide AI employees
There are three good ways to handle an AI employee over a holiday: let its schedule skip the public holidays and dates you list, pause it until a set date so it starts again by itself, or keep it running but stop it sending anything until someone is back to read it. Choose by what its work is for. A daily lead list nobody will read can skip the days; a road closure alert for a site that stays open should keep running; an employee that writes to customers should usually wait for you.
This article is for anyone who runs AI employees in xMap Flows and is about to take time off, close for a public holiday or shut down for a season. It covers the three options, how each one treats work in progress, a made-up example of a team planning its year-end, the mistakes that cause surprises and a short checklist.
Option one: skip holidays and dates in the schedule
The Schedule block can leave out the public holidays of a country. A run due on a holiday is skipped and the next one runs as usual. It holds holiday lists for 51 countries from 2026 to 2028. Holidays that follow the moon are approximate, because governments announce the exact dates each year, so add those under the dates to skip once they are known.
You can also list your own dates to skip: a company shutdown between two dates, an inventory day, a long weekend that is not a public holiday. The schedule panel shows the next three runs before you deploy, so you can check that the skipped days really are skipped.
This suits employees on a timetable whose output only matters when people are working. Paired with Only new, nothing is lost: the first run after the break still sends only what it has not sent before.
Option two: pause until a date
Pausing stops an employee completely. On the Flows page it is one click, and deploying again is one click too. In the Team inbox you can write to the employee in plain words, such as pause until next week or pause until 6 January, and it pauses and starts again by itself on that day.
This suits employees tied to a season or a project, and any employee you would rather not think about while away. Some things to know about work in progress while it is paused:
- Scheduled runs stop. Nothing runs on its own until it is live again.
- Waiting runs wait. A run held at an Approval block cannot be approved while the employee is paused; it waits until it is live again.
- Outreach sequences wait. Follow-ups queued by the Outreach block are not sent while the flow is paused.
- Nothing is deleted. Results, runs, settings and history stay exactly as they were.
Option three: keep it running, but ask first
Some work should not stop: an alert about roadworks at a site that stays open, a chat page that answers customers, a watch on a rival that might open during the break. For these, keep the employee live but change how much it does alone. Set it to ask first, so anything it would send waits for a person's approval, or add an Approval block before the sending step and name who is on duty.
Results still collect while you are away, so the first morning back you have the full picture without anything having gone out unchecked.
A worked example
This example is made up. A small distribution company in Cape Town closes from 22 December to 5 January and has four AI employees.
| AI employee | What it does | Holiday plan |
|---|---|---|
| Morning call list | New shops for reps, weekdays | Skip dates 22 Dec to 5 Jan in the schedule |
| Road watcher | Closures near the warehouse, daily | Keep running; the warehouse has a skeleton crew |
| Outreach to new stores | First messages and follow-ups | Pause until 6 January from the Team inbox |
| Monthly market brief | A PDF on the 1st of each month | Keep running; nobody needs to act on it |
A made-up plan, to show how the choice follows the work.
On 6 January the outreach employee starts again by itself, the call list sends only shops it has not sent before, and the road watcher never stopped.
Mistakes that cause surprises
- Pausing an employee that sends alerts nobody else covers. If a site stays open, its alerts should keep coming to whoever is on duty.
- Forgetting to start it again. A paused employee stays paused. Pause until a date, or put a reminder in your calendar.
- Relying on moon-based holiday dates. They are approximate; add the announced dates yourself.
- Leaving follow-ups to land on the first day back. A batch of messages all sent the morning you return can flood replies. Spread them, or approve them in groups.
- Not checking the next runs. The schedule panel shows them. Look before you leave.
A checklist before you go
- List your AI employees and write next to each: skip, pause or keep running.
- For skip: add the holiday country and your own dates in the schedule, and check the next three runs.
- For pause: write pause until and the date in its Team inbox thread.
- For keep running: set it to ask first, or add an Approval block with the person on duty.
- Check that every employee writing to customers is paused or asks first.
- On your first day back, read the Team inbox for each employee's notes before anything else.
Templates such as Morning call list with decision makers, New places every morning, only new and Morning site briefing: weather and road closures all run on a schedule you can set to skip holidays.
Questions
Can an AI employee skip public holidays automatically?
Yes. The Schedule block can leave out the public holidays of a country, with lists for 51 countries from 2026 to 2028, plus any dates you add yourself.
If I pause an AI employee, do I lose its results?
No. Pausing stops new runs only. Results, runs, settings and history stay, and deploying again is one click.
Can I pause an employee until a set date?
Yes. Write pause until and the date, or pause until next week, in its Team inbox thread, and it starts again by itself on that day.
Will the first run after a break send everything again?
Not if the flow has an Only new block. It sends only what it has not sent before, so the first list back is still a list of new things.
What happens to approvals waiting while an employee is paused?
They wait. A run held at an Approval block cannot be approved until the employee is live again.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates