Account

Troubleshooting and support

Check the current workspace, release, and recorded error before retrying.

1. Check the active workspace, your role permissions, and subscription access. New business tools are grouped under Operations.
2. After a stale-form or version-conflict message, reload and review the current saved record before submitting again.
3. For delivery, scheduling, or integration problems, inspect the recorded status and diagnostic reference. A queued job or cron email alone does not confirm the intended work completed.
4. If an uploaded update still looks old, compare the build shown in the footer across the app, marketing site, and help site. The CP18 release shows 2026.09-cp18.5.
5. Ask the deployment administrator to verify the correct document root and complete upload, then refresh Laravel’s compiled views or route/config caches and the hosting panel’s PHP OPcache as needed.
6. Open Tools → Support with the page, task, approximate time, build, and reference code. Exclude passwords, private invitation links, tokens, and payment credentials.

Still need help? Open Support in your workspace and include the task, page, and any reference code shown.