The installation guide expects the WHMCS cron every five minutes. Use the correct command-line PHP for the installed WHMCS and module release, with its required extensions and access to the persistent secrets directory. Check the system account, filesystem permissions and environment used by the scheduler.

1. Confirm WHMCS reports its normal cron running as expected.
2. Open Workspace > Jobs & runtime and inspect queued, running, failed and recently completed jobs.
3. Open DNS Manager > Tasks & cron for DNS-specific schedules and maintenance controls.
4. Submit a harmless controlled DNS change and verify that it progresses to a final state.
5. Review the module's diagnostics and resolve runtime, provider or key-access errors.

A future scheduled change is expected to wait. A repeatedly queued immediate job may indicate a missing worker, lock or dependency. A failed provider operation requires its specific error to be addressed. Compare timestamps and job references rather than treating all three cases as a propagation delay.

Premium monitoring also depends on the scheduler. Checks, failure thresholds, recovery thresholds and record TTLs make up the total user-visible response time. Do not promise minute-level results while cron is stalled.

The delivered console includes diagnosis, migration and worker commands such as diagnose, worker and worker:once. Follow the installed release's usage instructions and run them as the authorised system account. Do not launch competing permanent workers simply because one job is delayed.

Keep secrets out of command arguments and log output. A web process and a cron process can have different PHP configurations or environment variables, which is particularly relevant for reseller connectors using environment-held credentials.

After fixing the underlying issue, inspect the existing operation before retrying it. A registrar or DNS provider may have completed a request whose response was lost. Use reconciliation and the supported retry workflow, preserving the original business reference.

Record recurring failures and alert on jobs that remain stalled beyond your operational threshold. A periodic check of completed work is more reliable than monitoring only whether the WHMCS homepage loads.

• Install Domain Nexus in WHMCS and initialise its secure storage
• Review and apply DNS changesets with a clear recovery path
• Resolve DNS drift and changes with an unknown provider outcome
• Create Premium DNS products and configure their actual paid features