1. Open the application account list in App Hosting and locate the service by customer, domain or service reference.
2. Read its setup state. The current workflow distinguishes Ready, Installing, Needs attention, Not started and Customer installs.
3. Open the WHMCS service record and confirm its server, hosting username, product and account status.
4. Check the selected application policy, server package and installer availability. Review the most recent safe error details before submitting another action.

If the WHMCS service is still pending and the hosting account has not been created, use the normal WHMCS Create action after correcting the provisioning problem. If the account already exists and the application setup is incomplete, use Continue setup where available.

The continuation workflow is designed to inspect existing and pending installation work, including adopting an installation that already completed. This matters when an earlier request succeeded on the server but the response did not reach WHMCS. Refresh the application list and inspect the destination path before treating the account as empty.

Typical checks include whether the selected application exists in the server catalogue, whether the package is available on the assigned server, whether WP Toolkit or Softaculous responds, and whether the domain, PHP version, quota or target directory prevents installation. Correct the specific condition reported by the provider.

For a product configured with Hold the order if setup fails, incomplete required installation affects provisioning completion. For a product where the customer installs later, Customer installs can be the expected state. Do not confuse a deliberate policy with a fault.

After continuing setup, check the resulting website, application administration access and customer tools. Confirm the account list reaches its expected state and that the welcome message accurately describes what is ready.

The normal WHMCS cron can retry eligible unfinished setup, within the module's retry limits. It is not a reason to ignore a persistent error or assume an exact completion time. Keep the cron healthy, but intervene when the same configuration error recurs. Record the cause and the recovery action so your team can distinguish a corrected account from one still awaiting customer input.

• Create a hosting product for one selected application
• Configure and verify the WHMCS cron for Hosting Suite
• Change, duplicate or convert an application hosting plan
• Prepare a cPanel server for managed WordPress plans

• WHMCS service administration
• WHMCS: setting up the system cron