# Questions

> **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).

## Auto Schedule

### Does Auto Schedule change my roster?
No. [Auto Schedule](https://chrona365.com/glossary/auto-schedule) returns a proposal. **Apply** saves it; **Discard** leaves your roster unchanged.

### What data leaves my environment?
A copy of the period you plan. Workers travel as placeholders, with their roles, hours, agreement rules, unavailable, preferred and unpreferred time, and the available time of each worker with a pattern. No names, notes or contact details leave. The **Auto Schedule** dialog shows the exact data before your first run.

### How many runs can we make?
As many as you need, within fair use. Each run gets time in proportion to the size of your roster and stops when it stops finding a better one. Your organization can have two runs going at a time.

### Why are shifts still open after a run?
No worker met the role, **Must** skills, groups, availability, hours, agreement Must rules and overlap checks. Select **Why not…?** on the shift to check a worker. Add eligible workers, change the shift or assign it manually. See [Auto Schedule](https://chrona365.com/docs/workforce/auto-schedule#ask-why-not).

### How do I stop Auto Schedule moving a shift?
Pin it. A pinned shift stays as it is: same times, same worker.

## Rostering

### Who uses the app?
The workers who plan and set up the roster. They hold the role **Chrona Workforce User** or **Chrona Workforce Admin**. See [Install Chrona Workforce Scheduler](https://chrona365.com/docs/workforce/install). The workers you roster are rows in **Workers**.

### Why does the board ask for a reason when I drop a shift?
The move breaks a Must rule of the worker's agreement or a rule set to **Don't allow**; the board names the rule and asks for your reason before it saves: see [Assign anyway](https://chrona365.com/docs/workforce/call-out#assign-anyway). **Cancel** puts the shift back. Open **Schedulers**, your scheduler, then the board's gear > **Rules** to check **Skill rule**, **Availability policy**, **Overlap rule** or **Working hours rule**. **Warn** permits a move with a warning.

### Why does a worker get no shifts?
A worker with an availability pattern gets shifts only inside it. Check their pattern, or their employment type's default, on the **Availability** page under **Workers**. Add one-off **Available** time on the worker's **Availability** tab. Check their groups too: a worker works only shifts of their groups, or shifts with no group. See [Patterns](https://chrona365.com/docs/workforce/availability#patterns) and [Groups](https://chrona365.com/docs/workforce/roles-and-skills#groups).

### Where do the new open shifts after a run come from?
From your demand. When nobody can work a shift the demand needs, **Apply** saves it as an open shift that needs cover. Your workers can pick it up like any open shift. The next run adds open shifts only for what is still short. See [Demand and coverage](https://chrona365.com/docs/workforce/demand#shifts-made-from-demand).

### Can my workers pick their own shifts?
Yes. In [self-rostering](https://chrona365.com/docs/workforce/self-rostering), workers pick open shifts and coverage days in Mobile and star their priorities. At close, Auto Schedule keeps stars, prefers other picks and fills remaining work. You review the Draft roster and publish it.
### Who gets an open shift first?
For ordinary open-shift requests, **Review open-shift requests** decides: approval by a manager or the scheduler's planners when on; the first eligible worker to accept when off. A call-out for lost cover offers the shift in ranked levels to the scheduler's eligible workers. Select **Candidates** to see the ranking and why. See [Candidates and call-out](https://chrona365.com/docs/workforce/call-out).

### Does a scenario change my roster?
No. **Scenarios** plans copies of the period. Nothing changes until you select **Use this roster** and then **Apply** on the board. See [Scenarios](https://chrona365.com/docs/workforce/scenarios).

### Will Generate overwrite my changes?
No. Generate adds the shifts that are missing and removes the extra shifts nobody has touched. A shift that you edited, assigned or pinned stays, with a note.

### Why is there no Generate button?
**Generate** shows on the board when your scheduler has coverage. Open **Schedulers**, open the scheduler, select the gear on its board and check that **Coverage** has rows in [Shift types and coverage](https://chrona365.com/docs/workforce/scheduler-settings#shift-types-and-coverage). See [Shift types, coverage and Generate](https://chrona365.com/docs/workforce/templates).

## Billing

### Does a proposal count towards billing?
Yes. A worker counts once a month when Auto Schedule schedules them, however many shifts, calendars or environments, whether or not you apply or publish the proposal. Runs themselves are not charged, and shifts you roster by hand do not count. The first five workers each month are free. See [Plan and billing](https://chrona365.com/docs/account/billing).

### What happens above five workers without a trial or subscription?
Auto Schedule and Generate pause until you start the 14-day trial or subscribe in the Chrona Portal. Rostering by hand, editing, publishing and Chrona Workforce Mobile keep working, and no data is locked.

### What happens if a payment fails?
Everything keeps working with a warning until the date that **Plan and billing** shows. After that, Auto Schedule and Generate pause until the invoice is paid. Rostering by hand, editing and publishing keep working, and no data is locked.

---
Product: Workforce Scheduler
Language: English
Canonical: https://chrona365.com/docs/workforce/faq
