Investigate a failed HostBill task by identifying its target, the action requested and the provider's actual result. A queued operation failing locally does not always mean that nothing happened remotely.
01 Diagnose the failure
- Open Extras > System Logs > Task Queue Log. Locate the task by its time and target account, order or domain. Record the task ID, description, status and error.
- Open the related account and review its Account Log and automation queue. Check whether another staff member or task already attempted the same action.
- Determine the failure layer. Missing PHP extensions or unreadable files affect the worker; invalid credentials or unavailable packages affect the integration; an unpaid or unaccepted order can fail the workflow's prerequisites.
- Check the provider directly using an authorised account. For a creation request, look for an existing account or resource with the expected identifier. For a renewal, inspect the provider's expiry date or transaction history.
- Correct the specific cause. Test connectivity without creating another billable resource where possible, then choose the appropriate retry or reconciliation action for the existing HostBill record.
- Monitor the next queue processing interval and confirm that the task resolves and no duplicate resource appears.
02 Escalate with usable evidence
Record the HostBill version, module, task ID, affected service ID, timestamp and timezone, provider request identifier and exact redacted error. Keep credentials, tokens and customer data out of a public troubleshooting post. State what the provider shows so the next operator does not repeat a completed request.
Common questions
Should I delete all failed tasks to clear the dashboard?
No. First establish what each failed task represents and whether an account still needs recovery. Removing evidence can conceal an unprovisioned paid service or a renewal that was never completed.
What if the queue is moving but one account remains stuck?
Focus on that account's prerequisites and provider response. A functioning queue does not fix a missing package, insufficient provider balance or a service identifier that points to the wrong resource.