Description

Takes up to 50 queued webhooks and applies each one: connecting customers to accounts, recording transactions, creating Access Subscriptions and licenses, adding groups and sending emails. Events about the same transaction, subscription or customer are applied in the order they happened, and an event older than one already applied is skipped. If 50 were processed and more are waiting, the task carries on at once.

At the end of each run it also sends the emails about customer conflicts that processing recorded: the claim link to the customer and the alert to administrators (see the section called “Customer Conflicts”). An email that can't be sent is tried again at the next run, five times in all.

An event that fails for a reason that may pass is tried again later, waiting 30 seconds, then 1, 2, 4 and 8 minutes, six tries in all, after which it is given up. An event that fails for any other reason is not retried; the log says why. Events are deleted 60 days after they arrived.

While PaddleSubs is offline (Offline Enabled on, or no API key for the current environment), the task processes nothing and succeeds; the webhooks wait in the queue until Paddle is connected.

Schedule

Every minute. Until it runs, customers who have paid don't get access.

Options

None.