Troubleshooting is safest when you first isolate the workspace, browser, connection, permission, and feature involved. Avoid changing or deleting data while the cause is unclear.
The names of buttons and sections can vary with your PloverCRM plan, permissions, connected services, and current version. When a label differs, use the matching label displayed in your account and do not change an unrelated setting.
Safe troubleshooting order. Confirm the correct account, workspace, connected website, browser, and user role. Record the exact non-sensitive error, affected screen, approximate time, and last successful step. Check the relevant status page or log before changing configuration. Make one low-risk correction at a time and wait for the result. Verify the result before retrying or escalating Do not delete records, reinstall plugins, reconnect integrations, or rerun imports merely because a page looks stale; these actions can change data or create duplicates
- Write down the feature, workspace, browser, approximate time, and exact non-sensitive symptom.
- Confirm that you are signed in to the PloverCRM Web Dashboard and selected the intended workspace.
- Check the connection, plugin, data source, account, and role required for the affected feature.
- Repeat the action once and record the exact non-sensitive message or status.
- Apply the troubleshooting step that matches the symptom, then wait for the result.
- Refresh or sign in again only after saving or canceling any pending work.
- Check the relevant log, status page, or record to confirm whether the problem is resolved.
- Contact support with safe diagnostic details if the issue remains.
What to verify #
After the final step, confirm:
- The workspace name and connected website still match the intended destination.
- The status, record, filter, setting, or result reflects the change you made.
- No unrelated lead, teammate, connection, message, or automation was changed.
- Any export, notification, file, or external action follows your organization’s privacy and retention policy.
PloverCRM should display a confirmation, updated status, or refreshed record. If the workflow is asynchronous, use its progress or log view instead of submitting the same request again.
Troubleshooting #
- If the screen or control is missing, confirm the workspace and ask an administrator to review your role.
- If results are empty or stale, clear filters, refresh once, and check workspace connection status.
- If a value is rejected, read the field-level message and use the required format.
- If an operation is processing, wait for its status or log entry before trying again.
- If the result is unexpected, stop before making another change and record the exact non-sensitive message, approximate time, browser, and reproduction steps.
