A safe maintenance procedure
Use an administrator account, make a current backup before structural changes, and never paste passwords or complete API or licence keys into screenshots or support requests.
What this guide covers
- Where to find every control used in this workflow
- What each setting changes and when to use it
- How to verify the result before relying on it in production
- What evidence to collect if the result differs from the expected behaviour
1. Prepare
Read the exact product release note and confirm requirements.
Procedure
- Create and verify a database/files backup.
- Record the current plugin, WordPress, PHP and WooCommerce versions.
- Use staging first for a business-critical site.
A recoverable restore point exists.
2. Update and test
Apply one relevant change at a time.
Procedure
- Update the NextlerAI product.
- Clear WordPress, server, CDN and browser caches.
- Run licence/provider diagnostics.
- Repeat the product’s critical workflow.
The expected version runs without new errors.
3. Recover
If a regression is confirmed, restore the known-good package and data consistently.
Procedure
- Capture the failure evidence.
- Disable automation or public chat if needed.
- Restore the package or complete backup according to the change scope.
- Report exact reproduction details.
Service returns to the known-good state.
Final verification
- Save the configuration and reload the screen to confirm it persisted.
- Test in a private browser session so administrator state and old cookies do not hide the real visitor experience.
- Test one normal case, one boundary case and one deliberate failure.
- Review the relevant product log, job, report or diagnostic screen.
- Record the installed product, WordPress, PHP and WooCommerce versions with the test result.
Troubleshooting checklist
- Confirm the licence is active for this exact product and environment.
- Check provider access, billing and model availability.
- Clear every active cache layer after settings or content changes.
- Verify background processing and inspect the first error, not only the final symptom.
When to contact support
Contact support only after repeating the test with caches cleared and current versions. Include exact steps, expected and actual results, the safe error text and a diagnostic export when available. Mask licence and API keys; do not send customer personal data.