Scheduled jobs
They run inside the backend, in the server's time zone.
Generated by
scripts/generar-referencia.mjs. Do not edit by hand.
They run inside the backend, in the server's time zone. The schedule is a time
of day (4:00) or an interval (cada 15m, cada 2h, meaning every 15
minutes or every 2 hours). There is no cron: the scheduler rejects any other
form at startup.
| Job | Schedule | What it does |
|---|---|---|
limpiar-reservas-huerfanas | 4:00 | Releases stock reservations whose order line no longer exists and recalculates the reserved quantities |
borrar-soporte-antiguo | 4:00 | Deletes resolved store support conversations older than the retention period |
cerrar-soporte-autor | 4:00 | Closes author support threads the buyer left unanswered and deletes closed ones past the retention period |
borrar-personalizacion-caducada | 4:00 | Deletes from disk the customisation files customers uploaded once their retention period is over |
caducar-puntos | 4:00 | Expires the loyalty points batches that are past their date |
cuadrar-pagos | 5:00 | With a payout rail set: re-checks stuck author payouts, retries pending splits and compares our ledger with the provider's |
avisar-carritos-abandonados | cada 15m | Marks idle carts with email and items as abandoned, once, and emits the plugin event carrito.abandonado; sends no email |
purgar-limites-de-intentos | cada 2h | Deletes expired rate-limit counters |
repasar-boletin | cada 30m | Brings in the unsubscribes made on the email service and sends it the subscriptions and unsubscribes it does not know about yet |
Modules and their tables
Every migration, in the order it is applied, with the tables it creates or changes and the module it lives in.
Theme contract — pcreative Commerce
The standard every storefront theme meets so they are interchangeable, customisable from the panel and updatable without losing the customer's…