Contents
What Happens Without You
Three kinds of work happen in the background, all as Joomla scheduled tasks:
- Processing webhooks
-
Paddle's webhooks are saved in a queue the moment they arrive, and the PaddleSubs - Process webhooks task works through it, up to 50 at a time. Events about the same thing (one transaction, one customer) are applied in the order they happened, and an older event that arrives after a newer one is skipped. If an event fails for a reason that may pass, for example because the database was busy, it is tried again later, waiting longer each time (from 30 seconds to 8 minutes), six tries in all. Processed events are deleted after 60 days.
- The lifecycle
-
The Access subscription lifecycle task starts and ends Access Subscriptions on time, asks Paddle whether the payments behind them have since been refunded or charged back, and adds and removes groups. It also starts pending imported Access Subscriptions whose window has opened, and ends imported and granted ones whose window is over.
- Reminders
-
The PaddleSubs - Expiry reminders task emails customers before and after one-time access ends.
Some purchases can't be turned into access automatically, and are set aside (quarantined) instead of guessed at: a purchase whose customer can't be matched to a Joomla account, of a product or price your site doesn't know, of a custom price made for one customer in Paddle, or a change to a Paddle subscription that doesn't say which period it pays for. The log records each one, and the Needs Attention page lists those still waiting, where you can try them again once the cause is fixed.