# Crons
The system has a 4 crons. These crons perform long-lasting tasks that would not be good to perform on every single call to the api.
# Processor
The processor cron is responsible to turn unused bookings into visits. There is a difference between ASSQ and CSC on how to handle these newly created visits. It runs every morning at 8am
# ASSQ
The ASSQ, for administrative reasons, deletes all free bookings. The bookings that have been paid with cash or gift cards on the other hand, they stay as bookings, they can be moved to a later date by the association.
# CSC
The CSC, count that visit as used for the customer but cancelled for the resort, again, for administrative purposes.
For exact details on this feature please see the
google docs (opens new window)
about it.
# Giftcards
This cron is responsible for deducting service fees every month after the 19th month of activation of a gift card.
For now, this has been put on hold and has not been implemented.
# Dashboard
This cron is responsible for generating every resort and the association's dashboard information. This helps keep the dashboard lightning fast and as close as possible to factual data. It runs every night at 3am.
# Refunder
This cron is responsible for the mass refund feature. It runs every 15 minutes and works with a queue of requests to perform. This queue is broken into 250 refunds per 15 minutes as to not flood stripe with this work.
It will only run 1 mass refund request at a time, once a task is completed, it gets removed from the queue and the new request can be performed the on subsequent runs. It runs only when asked.
# Processor
This cron is responsible for processing all the bookings that have not been used when they were supposed to. It will take them and process them the with each association's requirements. It runs once every day.
# PowerBI
This series of cron are responsible for building up the CSV files that PowerBI consumes every day to build it's database for reporting. They run once every day.
# Queue
This cron is the Queue Processor. It's responsible for processing tasks that have been set for it. For example, sending emails to targets of messages, send invitations to renew provincial passes, etc. This runs every 2 minutes.