Trigger
Paid orders, renewals, overdue states and manual service actions start the workflow.
Automation & Provisioning
Fulfillment starts when payment clears
WISECP turns paid orders, renewal dates and service events into queued work, executes module actions and keeps retries, errors and manual controls visible inside one observable automation system.
Automation Control Plane
One event can move the entire service forward
A paid order, due date, overdue state or staff action becomes a job with a clear execution path and a visible outcome.
Queue
Jobs carry attempt counts, worker ownership, heartbeat state and the next retry time.
Module Action
Create, suspend, unsuspend, terminate, reinstall or rebuild the service through its module.
Follow-Through
Update service state, continue child jobs and send the matching client notification.
Resilient Job Trace
Retry the failed action, not the whole order
Each queued job carries its own attempt history. Idempotency keys guard against duplicate work, while worker heartbeats and next-retry timing keep execution observable.
- Results, Info, Payload and Attempts keep each run inspectable
- Failed module jobs remain visible and can be retried
- Parent and child jobs preserve the execution sequence
Illustrative Job DetailOrder #12458
Worker Active
Payment ConfirmedOrder trigger accepted
Completed
Create ServiceModule returned an error
Failed 1/3
Retry ScheduledSame job, same idempotency key
Next Run
Create ServiceSecond attempt completed
Completed 2/3
Welcome NoticeNotification Queue
Completed
Heartbeat 00:01.2
Parent #12458
Service Lifecycle
Keep automation under operator control
Automation handles routine state changes, while staff can inspect the service record and intervene when a case needs judgment.
- Create, suspend, unsuspend, terminate, reinstall and rebuild
- Day-based lifecycle rules with manual action controls
- Scheduled downgrade cancellation before execution
- Cancellation requests with priority and reason, plus approval-based service transfers
Upgrade and downgrade requests move through Pending, In Process, Scheduled and Completed states, with proration and refund options.
Automation Dashboard
See every scheduled task, every run and every outcome
A searchable catalog of 72 registered tasks brings billing, services, domains, support and infrastructure work into one control center.
Billing & Collections
Invoice generation, metric invoices, Auto-Pay, reminders, overdue notices and late fees.
Service Lifecycle
Suspension, metered suspension, cancellation, server termination and request processing.
Domains & SSL
Renewal and expiration notices, grace and redemption handling, relock, transfer sync and SSL expiration.
Support & Notifications
Email Pipe, ticket automation, auto-close, bulk notifications and the notification queue.
Infrastructure & Housekeeping
Module jobs, metric collection, cloud cost and stock sync, backups, retention and cleanup.
System Status
See the last run, upcoming job, active work, pending work and failures.
Task Filters
Narrow the catalog by issues, pending work, active tasks or disabled tasks.
Job History
Filter execution history by task, stage, period and completion state.
Job Detail
Inspect Results, Info, Payload, Attempts and parent or child relationships.
Automation Settings
Turn timing into operational policy
The Settings side of Automation separates worker health from the business rules that govern invoices, services, support and housekeeping.
Crontab FrequencyEvery minute
Install through the hosting panel, CLI or cURL, then connect external monitoring with the protected monitor URL.
Hosting Panel
CLI
cURL
System
Worker setup, processing window, job retention, external monitoring, cleanup and Cron Secret.
Invoices
Creation timing, three pre-due and three overdue reminders, cancellation, cleanup and late-fee policy.
Products & Services
Suspension, metered suspension, cancellation, server deletion, stale orders and domain notices.
Support System
Choose when inactive tickets close automatically and when closed tickets become locked.
Other Settings
Schedule log cleanup and remove unverified or empty accounts after your chosen delay.
Service Operations
Act on the fleet without losing individual context
Service state, placement and infrastructure health stay visible around the jobs that change them.
- Track payment and lifecycle state from the service list
- Use server groups and fill strategy for automatic placement
- Watch utilization and profitability at server level
- Import existing accounts and test connections before provisioning
Queue Foundations
Visibility is part of the automation engine
The queue records enough execution context to diagnose a stalled job, retry it safely and understand where it belongs in the wider workflow.
Idempotency
Unique job keys prevent the same queued action from being created twice.
Worker Heartbeat
Worker ownership and heartbeat state make active processing visible.
Retry Policy
Maximum attempts and next-retry timing keep failures controlled.
Execution Record
Results, metadata, payload, attempts and parent-child links stay with the job.
See It in Context
Watch an order move from paid to live
Open the Automation Dashboard, inspect a task and follow its job record into service provisioning in the live admin demo.