The old page creates bookings one at a time and ties up the browser. Generate Bookings runs in the background — you can start a batch and come back later — and lets you review every booking before it lands in the database.

There's no hard limit. The system processes entries in chunks behind the scenes so even very large batches (tens of thousands of entries) work without timing out. Larger batches take proportionally longer.

The entry was validated successfully at some point, but a change has been made to something it depends on (the client, the schedule entry, a carer's availability) since then. Click Revalidate now to re-check.

After a batch has confirmed, "Skipped" counts valid entries you deselected at confirm time — they were never turned into bookings.

Once the first one reaches the Confirmed / Creating phase, anyone else trying to start a batch over the same schedule entries will see a red blocking panel. See "A batch covering these schedule entries is already creating bookings".

Yes — once created, batch bookings behave like any other booking. They're not linked back to the batch from the booking screens.

Bookings already created stay in the database. Entries that hadn't been processed are marked Failed. The batch ends in Cancelled. Use Retry as new batch to pick up where you left off — the retry skips already-created bookings.

The chart only counts entries that already have an active schedule entry on the date. The batch additionally filters by active service contract, suspension status, and existing bookings — so the batch's number is normally a bit lower.

The Generate Bookings list shows the Created by column for every batch. The batch's detail sidebar shows the same.

If web push notifications are enabled for your account, you'll get a notification on Completed, Partially completed, and Failed. Failed batches also send an email.