Recurring Orders

What this page is for

Recurring Orders is where standing orders live: the same pickup, the same drop-off, on a schedule. Dispatchers and up open it from Recurring in the left rail.
Every template is posted by one of two things:

CXT: a CXT pre-schedule. CXT's Scheduler posts it (today that's the morning Post in XDispatch). StatVault copies every CXT pre-schedule in nightly between 2am and 4am in your organization's own timezone (each organization is copied with its own CXT connection) and shows it here read-only, because the next nightly copy would overwrite any change made here. A posted CXT ticket carries "Scheduler 123456" in its CSR field, and that number is how StatVault ties each day's ticket back to its template.
StatVault: a template StatVault posts itself at the posting time. Either it was created here, or it was a CXT pre-schedule that someone took over (see below).

Whichever one posts it, every template gets the same calendar, one row per date: planned, posted, skipped, moved, un-posted or failed. Once the day is done, it also shows whether anything was actually picked up.

The top of the page

Post now…: post every planned StatVault occurrence for a day immediately, whatever the posting time. It never posts CXT pre-schedules.
Un-post a day…: see Storms and closures below.
+ New standing order (admins): opens the New Order form in Standing order mode. Save it, then choose the schedule and posting in the panel and press Create template. To start from an existing order, use the calendar icon on that order (or Make it recurring → on its New order from… sheet).
Four tiles:

- Today: how many standing orders posted today, how many CXT posted, and when the first one landed.
- Tomorrow: how many are planned, and any blackout.
- Dry runs · last 30 days: the share of posted standing orders that were NOPU (the driver found nothing, entered 0 pieces) or cancelled. Click it to list the ones that were dry on half or more of their days.
- Needs a look: how many standing orders are mostly run by someone other than their standing driver. Click it to list them.

Under the tiles, one line says whether StatVault auto-post is on, when it posts, and the last posting run (Open shows each order it made or refused).

Times follow your clock setting: 24-hour or 12-hour, set on your Account page.

Standing orders tab

The list is grouped by customer (each group shows its count and average dry-run rate). Columns: CXT #, Origin Name, Origin Address, Destination Name, Destination Address, schedule ("Mon–Fri", "Tue, Thu", "Every 2 weeks: Mon", "3 dates"), pickup window, driver, 2 weeks, Dry 30d and who posts it.

2 weeks is a strip of the last 7 days and the next 7, with today outlined: green = posted, amber = dry run, hollow = planned, a thin grey dash = skipped or un-posted. Weekend days are narrower.
Dry 30d is the share of the last 30 days' posted orders that were NOPU or cancelled; 30% and up is amber, and a standing order dry on half or more of its days gets an amber row.
Under the driver, a blue line such as Nesi runs it 5 of 8 means someone else ran it on at least 5 of the last 8 posted days.
Click a column heading to sort; click again to reverse. Rows sort within each customer group, and the sort is remembered.
Filter with the search box (origin, destination, address, CXT #), the customer picker, and the chips: All, Posted by CXT, Posted by StatVault, Mostly dry, Needs a look (driver suggestions, failed posts, take-overs waiting on CXT) and Inactive.

Click a row to open the popout:

Header: origin → destination, who posts it, the schedule, the pickup window, the CXT number, and the main action: Post from StatVault… on a CXT pre-schedule (admins), Edit order… on a StatVault one.
Next 2 weeks: one tile per date with its state. On a StatVault template, click a day to Skip it (with a reason), Move it, Change that day only (time, pieces, driver), Restore it, or Retry a failed post.
Who really runs it: the drivers of the last 8 posted days as initials (the most frequent one filled in). When someone other than the standing driver ran it on at least 5 of those 8 days, the box turns blue and offers to make them the standing driver (StatVault templates) or to dismiss the suggestion. Nothing changes automatically.
The order that posts: origin and destination cards (name, address, remarks, windows) and the type, pieces, caller, references, holiday handling and start date. Edit order… (admins, StatVault templates) opens the same New Order form used to place any order, in its violet Standing order mode; what you save there is exactly what posts each day. A CXT pre-schedule shows CXT's own order, copied in nightly.
Schedule & posting (StatVault templates, admins): repeats every weekday, every N days, weekly on chosen days (every N weeks), monthly (days of the month, L = last day) or on specific dates, with start and optional end dates and a live preview of the next ten dates (blackout dates struck through); then the standing driver, holiday handling, an optional posting-time override and lead, and an optional Notice before pickup in hours (empty = the organization's setting; see When a standing order posts below).
Last days it ran: one bar per posted day, tall green = picked up, short amber = NOPU / cancelled.
History: date, order (opens it), driver, status and notes.
Notes appear at the top when pickups consistently happen 45+ minutes away from the ready time (drift), or when the last ten or more posted orders were all dry runs.

Calendar tab

A grid of templates × 14 days: · planned, ✓ posted, – skipped, → moved, ✕ un-posted, ! failed. A dashed box means a dry run. Blackout days are shaded. Click a template name or cell to open it, and click a day header to add a blackout, post that day now, or un-post it.

Runs tab

Every posting run: on schedule, Post now, retries, and un-posts. Open a run to see each order it made or refused, and why. Retry failed re-posts only the failures.
Refusal reasons you may see: blackout (a closure that day), cxt_still_live (a taken-over template whose CXT schedule hasn't ended yet), cxt_already_posted (CXT already posted it that day), already_posted, template_inactive, and cxt_transport_unverified (the organization is on CXT and posting into CXT isn't switched on in Settings).

Blackouts tab

Holidays and closures, either for everyone or for one customer. A blackout is one of three kinds:

Holiday schedule: standing orders that follow blackouts skip the day; ones set to Post through holidays still post (for example Memorial Day, July 4th and Labor Day).
Closed: a total shutdown. Every standing order skips, even the ones set to post through holidays, except a specific dates template that lists that day itself (the "(H)" holiday lanes). Emergencies are still taken as ordinary orders.
Move: the day's orders post on another day instead.

Adding one updates every affected planned date right away. If orders were already posted that day, the page offers to un-post them. Removing a blackout puts the skipped dates back to planned.
Add the big six holidays… adds the next 13 months of the holidays a medical courier closes for: New Year's Day, Thanksgiving and Christmas as Closed, and Memorial Day, July 4th and Labor Day as a Holiday schedule. A Saturday holiday is observed the Friday before, a Sunday one the Monday after. Dates that already have a blackout are left alone, and each one can be removed or replaced afterwards. MLK Day, Presidents Day, Good Friday, Juneteenth, Columbus Day, Veterans Day, the day after Thanksgiving, Christmas Eve and New Year's Eve are normal days: that is what four years of CXT posting history show. Add one by hand if a year differs.
CXT keeps its own holiday table for the pre-schedules it posts. The calendar shows those dates as skipped when the blackout matches, and switches them to posted if CXT posts anyway.

Storms and closures (un-post)

Un-post a day… takes a date, a scope (everything, one customer, or a pickup site by name or address), and a reason. Check what this does lists exactly what will happen before anything changes:

planned StatVault orders are skipped;
posted orders, StatVault and CXT alike, are cancelled, in CXT too;
anything a driver has already picked up, has in transit, delivered, or scanned is never cancelled. It's listed as "not touched" so you can decide.

Every un-post is recorded as a run, with the reason and who did it.

Taking a CXT pre-schedule over

On a CXT template, admins see Post from StatVault…. Pick a start date (and optionally a standing driver). StatVault then:

ends the CXT schedule the day before the start date (a write to CXT), and reads it back to check it took;
posts the template itself from the start date.

If CXT can't be updated, the template shows ⚠ end in CXT. End the schedule in CXT by hand. StatVault won't post it until the nightly copy shows the CXT schedule ended, so the same order is never posted twice. Give back to CXT… reverses a take-over: re-enable the schedule in CXT first, then give it back.

When a standing order posts

StatVault checks every minute and posts each standing order on its own, at the earlier of two moments:

the posting time: the organization's (say 6:00am), or the template's own override, for the same day or the day before;
its pickup time minus the notice before pickup: the organization's setting, or the template's own.

So the morning batch is the latest anything posts, never the earliest. With a 2-hour notice and a 6:00am posting time, a 3:30pm pickup posts at 6:00am with everything else, a 7:30am pickup posts at 5:30am, and a long run given 12 hours' notice posts the evening before (a 6:45am pickup posts at 6:45pm). A standing order with a standing driver is assigned to that driver as it posts, and the driver gets the notification then, which is the point of the notice: nobody learns about a three-hour drive half an hour before it starts.
Notice set to 0 means the posting time alone. If one day's pickup time was changed (Change on the calendar), the notice counts from that day's time. An order posted the evening before belongs to the day it is picked up: the driver sees it on that day's manifest, not on tonight's.

Settings tab (admins change it)

Auto-post on or off, the posting time, and whether it posts for the same day (the default, because posting sends notifications to drivers' phones) or the next day.
Notice before pickup (hours): every standing order posts at least this long before its pickup opens, even when that is ahead of the posting time. 0 turns it off. Up to 72 hours; a template can set its own.
Plan ahead: how many days of dates to keep on the calendar (14 by default).
Posting into CXT: for an organization on CXT, StatVault-posted templates create their CXT orders through INet order create, which is metered: free under 5,000 orders a month. While this is off, StatVault refuses to post those templates.

When StatVault posts, each driver gets one notification per run ("14 standing orders for today") rather than one per order.

Things that confuse people

A standing order posted before the posting time is the notice at work: its pickup is closer to the posting time than the notice allows. Look at Notice before pickup in Settings and on the template.
Skipping a CXT date here doesn't stop CXT. CXT posts its own pre-schedules. Un-post the day after it posts, change it in CXT, or take the template over.
"Posted" on a CXT row means StatVault found CXT's ticket for that date, not that StatVault posted it.
Coverage ticket rows (CXT order type Route Coverage, such as "Need to Cover - Tom" or "Route Pay …") are coverage and pay tickets, not pickups. They get no dry-run rate, and Un-post a day never cancels them; they are listed as coverage_ticket under "not touched".
The old Billing → Recurring tab now just links here.
The customer record's Recurring tab shows recurring routes (Route Planner), which are a different thing from standing orders.

Coverage roster: who runs each standing order; roster rows carry the CXT pre-schedule chip.
Billing
Zippy tools: recurring_orders (read; ranks the driest standing orders over the whole list) and recurring_orders_edit (skip / move / restore / blackout).