> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opensubs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What runs without you

> Billing, retries, and emails run on schedule. Your job is two screens and the occasional reply.

OPENSUBS PLATFORM

* **Outcome:** you know what runs on its own, and the two screens that prove it.
* **Time:** a read, about 5 minutes.
* **Before you start:** [Live for New Orders](https://docs.opensubs.com/platform-v2/live-for-new-orders/what-today-changes.md) is behind you; if you switched platforms, [Migrate](https://docs.opensubs.com/platform-v2/migrate/what-actually-moves.md) too.
* **You'll touch:** the OpenSubs admin.

Every schedule below lives inside your own Supabase project, no vendor in the loop. Some work runs in your own app; if that app is down, those queues wait and drain when it's back. Every run is recorded.

| When | What runs by itself |
| - | - |
| Every minute | Queued emails and texts go out. Imports, bulk edits, and queued Shopify changes advance. |
| Every 15 minutes | A watchdog checks every job and queue, and opens an alert on **Settings > Operational health** when something stalls or fails. |
| Every hour | **Billing.** Each due subscription is charged after your store's clock passes the **Daily billing time** you chose in **Settings > Billing**. That time is a start, not a deadline: billing stays open for the rest of the day, so a subscription that comes due later still bills the same day. Timed pauses resume when they end; failed payments get their scheduled retries. |
| Overnight | Shipment reminders queue up, analytics snapshots run, multi-currency display prices re-sync from Shopify, and old records get cleaned out (some cleanups weekly). These run at fixed UTC times, so "overnight" is literal only for stores near UTC. |

A missed hour catches up on the next one; each due charge is picked up exactly once, so nothing double-charges.

Your two screens:

* **Home** shows a **Needs attention** banner only when something needs you: failed payments, or an open alert.
* **Settings > Operational health** shows alerts, connected providers checked live against their own servers, scheduled jobs, webhook delivery, and queue health. Alert checks re-run every 15 minutes; the panels read live when you open the page.

Most blips fix themselves: failed payments follow a recovery schedule you control, Shopify redelivers webhooks that didn't land, and queued work retries until it clears. [When an alert opens](https://docs.opensubs.com/platform-v2/run/when-an-alert-opens.md) matches each alert to its fix.

The group is organized by feature, each setup guide beside its what-went-wrong pages. [The morning check](https://docs.opensubs.com/platform-v2/run/the-morning-check.md) is the whole job most days, with [When an alert opens](https://docs.opensubs.com/platform-v2/run/when-an-alert-opens.md) directly beneath it. The one recurring chore, [updates](https://docs.opensubs.com/platform-v2/run/update-the-platform.md), closes the group.

![The schedule: every minute the queues drain, every 15 minutes the watchdog checks, every hour billing and retries sweep, overnight reminders and snapshots run. All of it reports to Home and Operational health.](https://mintcdn.com/opensubs-docs/T6NpYT9MdOxqnOk5/images/platform-v2/run/01-schedule-clock.svg?fit=max\&auto=format\&n=T6NpYT9MdOxqnOk5\&q=85\&s=b1abff563661ba6025a0a182a293ca57)

Four schedules, two screens. The machine works; the screens prove it did.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.