# Auto Task Log

> **Set up with an AI agent:** Connect Chrona MCP for documentation, setup guidance and configuration recipes. Server: https://mcp.chrona365.com/mcp (Streamable HTTP; authentication: None). Your agent needs separately authorized Dataverse tools to apply changes. In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools. [Connection guide](https://chrona365.com/workforce/install-with-an-agent).

Open **Configuration** > **Auto Task Log** to run tasks, review what changed and investigate failures.

## Turn on scheduled tasks

The **Chrona Scheduled tasks** cloud flow checks hourly and starts due tasks listed below. It is **on after an import in which the admin picked its connection**.

1. In the import wizard, pick your own Microsoft Dataverse connection for **Chrona Scheduled tasks Dataverse**, shared with **Chrona Call-out timer**. Both flows then run as you.
2. After an import from the command line or a pipeline, check this page an hour later. If tasks are overdue or a flow is off, follow step 7, **Turn on scheduled tasks**, in the downloaded install guide. Alternatively, use an application user to avoid depending on an individual.

While the flow is off, the tasks run only when you select **Run now**. The page says so, with the link **Open flow**: it opens the flow in Power Automate, where you turn it on.

An agent connected to the Chrona Model Context Protocol (MCP) server reads whether the connection is bound and the flows are on, and does the steps that are still needed. You sign in for the connection yourself. See [Install with an agent](https://chrona365.com/workforce/install-with-an-agent).

## The tasks

| Task | What it does |
| --- | --- |
| **Staffing check** | Adds open shifts when demand rises, and flags a drop for you to review. With **Fill new shifts automatically** on, **Auto Schedule** fills the shifts it adds. For each scheduler, it runs every **Check staffing every** hours (1 to 24; empty is 1). See [The staffing check](https://chrona365.com/docs/workforce/demand#the-staffing-check). |
| **Clean-up of old values** | Deletes demand driver values older than 90 days. The latest value before that stays, so the days after it still have a value to use. |
| **Clean-up of shift history** | Deletes a shift's history 90 days after the shift ends, once a day for each scheduler. The history records the unusual changes to a shift's worker: a shift given to another worker or left with no worker, a worker's accept, and a swap or cover. A run deletes at most 250 rows for a scheduler and leaves the rest for the next call. |
| **Self-rostering** | Runs each roster's pick window, for each scheduler with **Picks open** and **Picks close** set. From one hour before the window opens, it uses Generate to make open shifts from templates. When a demand window opens, it starts making its demand shifts. A later call collects a solve that is still running. When the window closes, it runs Auto Schedule with the picks and saves the roster as Draft shifts for you to check and publish. It runs at each hourly run of the flow. |
| **Call-out start** | Starts the call-out of each published open shift that lost its worker and has entered its scheduler's call-out horizon. It runs at each hourly call. See [Candidates and call-out](https://chrona365.com/docs/workforce/call-out). |
| **Clock-out reminders** | Sends one notice in Chrona Workforce Mobile to each worker still clocked in after a shift's planned end and **Minutes allowed after work finishes**, and an email or a text message when **Send by** in App settings turns them on. It runs at each hourly call. See [Clocking in and out](https://chrona365.com/docs/workforce/clocking). |
| **Exports** | Queues each automatic export when it is due, builds the queued export files and retries a delivery that failed. The flow checks each hour. See [Export hours and staffing reports](https://chrona365.com/docs/workforce/exports). |
| **Clean-up of export checks** | Deletes the results of an export's check once nothing can use them: a check that started 30 minutes ago or more, and the checks of automatic exports that no enabled export action waits on. It runs at each hourly call. |
| **Calendar refresh** | Tries again to refresh a worker's calendar feed when a refresh after a shift change failed. It tries at each hourly call, 30 minutes or more after the last try, up to 5 times. A run counts the feeds it tried. A worker's feed still failing after that shows on **Schedulers** for administrators, and the next change that writes the feed tries again. |
| **Directory sync** | Brings workers in from your directory. The flow **Chrona Worker directory schedule** runs it every 30 minutes while directory automation is on. See [Connect your directory to Chrona Workforce Mobile](https://chrona365.com/docs/workforce-mobile-directory). |

Each task shows **Last run**, status and any error. Except **Directory sync**, tasks also show **Next run**.

| Status | Meaning |
| --- | --- |
| **Not in use yet** | Staffing check needs a scheduler's [Staffing counted per](https://chrona365.com/docs/workforce/scheduler-settings#staffing-standards) driver; Self-rostering needs [Picks open and Picks close](https://chrona365.com/docs/workforce/scheduler-settings#self-rostering). |
| **Nothing waiting** | Exports or Calendar refresh has no pending work; it is never overdue. Otherwise **Next run** is the waiting work's due time. |
| Failed, running or skipped | Label beside the run time; failures also show the error. |

## Run a task now

Select **Run now** to start immediately and see what changed, including how many new shifts Auto Schedule filled or left open.

- After 45 seconds, an unfinished fill says **Filling open shifts, started**, with its start time and, for an earlier day, date. The next check or **Run now** collects the result.
- If Auto Schedule is already running for that scheduler, **Fill skipped** / **not filled yet** means the next check fills them.
- **Not in use yet** disables **Run now**. **Directory sync** has no **Run now**; the flow **Chrona Worker directory schedule** runs it.

## See what each run changed

Select **Show runs** to expand **When**, **For** and **Changed**. Counts identify added or published shifts, hours over standard, deleted values or history rows, or picks kept. Runs show **No change**, their error, or **Running** with the fill's start time. **Fill skipped** means another Auto Schedule run was active; the next check fills the shifts.

## When scheduled tasks stop

If Dataverse rejects an operation and rolls back the call, the call stops and its log rows may not be saved. Check the **Run now** error or the failed **Chrona Scheduled tasks** flow run. Correct that error before you retry. Other task failures that can be saved remain in the log; the call can then continue to the next task.

Chrona tells you when the scheduled tasks do not run or keep failing:

- **On the Auto Task Log**: when a task is more than 2 hours past its **Next run**, its **Next run** says **Overdue**, and the page says which task is overdue (or that tasks are, when more than one is) and to check that the flow “Chrona Scheduled tasks” is on. Select **Open flow** to open the flow in Power Automate, in a new tab. A task whose last run failed shows **Open flow** beside its error too.
- **In Power Apps**: when the log records 3 failed runs in a row for one scheduler, each Workforce admin gets an in-app notification. The app ships with in-app notifications on. Each admin who must get the notice needs a role that lets them receive app notifications, such as **Basic User**: see step 7 of the install guide in the download.
- **On the board**: when a scheduler's staffing check has not run for longer than its **Check staffing every** hours plus 2 hours, the scheduler's planners see the line "Open shifts may not match the latest counts. The staffing check hasn’t run since {date}. Ask a Workforce admin to check scheduled tasks." {date} is the day and time of the last run on the site's clock, in the board's hour format, for example "4 Nov, 09:12".

---
Product: Workforce Scheduler
Language: English
Canonical: https://chrona365.com/docs/workforce/auto-task-log
