ACE Training
Website

What runs automatically

← Back to the portal

Every job that runs on its own, when it runs, and who gets the email. All times are New Zealand time. They can run a few minutes late when the schedules are busy.

The website rebuilding itself

WhenWhat happensWho hears about it
7:56am The demo site rebuilds, so anything saved in Sanity can be checked before customers see it.
Why: so Tracey can change wording and see it before customers do. Nothing reaches the real site by accident.
deploy.yml, target demo
Nobody, unless it fails
9:56pm The live site rebuilds. Anything approved during the day goes to customers overnight, and prices and dates are refreshed from Administrate.
Why: course dates, prices and availability come from Administrate, so the site would drift out of date within a day without this. It also means a change approved late in the day does not wait for someone to press a button.
Also checks: the number of old addresses that forward to current pages. Cloudflare allows 2,000 and the site uses about 970. At 1,800 Rove gets an email so the fix is planned rather than a publish stopping.
deploy.yml, target production
Rove, if it fails
Rove, if the site nears its redirect limit

Pressing Publish to ace.co.nz in the portal does the 9:56pm job on demand. You do not have to wait for it.

Daily checks

WhenWhat it checksWho gets the email
6:17am Unfinished bookings. People who started a booking yesterday, midnight to midnight, and did not finish, with the course, date and why they stopped. Only sent on days there are any. If it cannot send, it tries twice more and then tells Rove.
Why: somebody who got most of the way through a booking is worth a phone call. Before this, nobody knew they existed.
abandoned-digest.yml
bookings@ace.co.nz for customers who stopped, with Rove copied for now
Rove for website or Administrate faults
3:04am Administrate check. Puts every kind of booking request through Administrate's own validation without creating anything, so a change on their side is caught before a customer meets it.
Why: in September, bookings failed for six days because Administrate started refusing something it used to accept, and the first anyone knew was a customer complaining. This finds that the next morning. It runs overnight so the answer is waiting at the start of the day.
adm-audit.yml
Rove, only when something fails
7:23am Pages not found. Every address a visitor could not find in the last 24 hours, with how they got there. This is how we found trainers still sending people to the old evaluation address.
Why: a link from the old site, a printed handout or an email can send people to a dead end for months without anyone noticing. Each one is a lost enquiry.
not-found-digest.yml
Rove

Weekly

WhenWhat it doesWho gets the email
Monday
7:12am
PD Training dates. Reads PD Training's public schedule and lists the dates Administrate does not have. It changes nothing.
Why: ACE sell 43 PD Training courses and Administrate holds no dates for them, so every one of those pages says no scheduled dates and cannot be booked. This is the first half of fixing that.
pd-training-dates.yml
Rove

Sent the moment it happens, not on a schedule

WhatWhen it is sentWho gets it
New booking Someone books and pays, or books by invoice bookings@ace.co.nzRove
ACTION NEEDED A booking cannot hold a place, so it has to be done by hand. Carries the company, attendees, phone, PO and invoice address bookings@ace.co.nzRove
Booking failed A booking fails on the website or Administrate side. Within the minute Rove only
Enquiries and in-house requests Someone sends a form on the website info@ace.co.nz
Sign-in codes for this portal Someone asks for a code The person signing in

Emails from the website come from ACE Training at the site's sending address. Course confirmations to customers come from Administrate, not from here.

Changing who gets what

Tell JP the address you want and he will change it. The addresses are settings on the website rather than anything in the page, so nothing needs rebuilding by you.