Provisioning is asynchronous. An order that is paid dispatches a provisioning job onto the queue; a worker picks it up and talks to the control panel through a driver. Nothing provisions inline with a web request, so a slow or unreachable panel never blocks checkout.
Drivers
| Driver | Talks to | Typical operations |
|---|---|---|
| cpanel | cPanel/WHM API | Create account, suspend, unsuspend, terminate, change package, read usage |
| plesk | Plesk XML/REST API | Create subscription, suspend, unsuspend, remove, change plan, read usage |
Enabled drivers are listed in HOSTINVO_PANEL_DRIVERS. Each driver has its own timeout and retry settings, so a slow panel can be tuned without affecting the other.
Job lifecycle
- 1
queued
The job is dispatched to the provisioning queue.
- 2
processing
A worker has picked it up and is calling the panel.
- 3
completed
The panel confirmed the operation and the service is active.
- 4
failed
The operation exhausted its retries. The job is retained with its error so it can be inspected and retried.
Retries and recovery
- Transient panel errors are retried automatically according to the driver's retry settings.
- A failed job can be retried by hand from Provisioning without re-placing the order.
- Usage figures are re-synced hourly for services that have gone stale, so disk and bandwidth stay current without polling every account continuously.
NoteProvisioning depends on the queue worker. If jobs sit in queued and never advance, check that the worker container is running before suspecting the panel.