Skip to main content

Environment troubleshooting

Common issues when connecting or maintaining Salesforce environments in Revsnap.

Screenshot coming soonenvironments-health-indicatorsEnvironment health indicators on the Environments page
Health indicators help you spot connection or token issues early.

OAuth redirect fails​

Symptoms: Browser blocks the redirect, or you see an error after clicking Connect.

Fixes:

  • Allow pop-ups for revsnap.forceweaver.com
  • Make sure you are logged into the correct Salesforce org before authorizing
  • For sandboxes, check Sandbox / test org in the connect modal before redirecting
  • Verify your Salesforce Connected App allows the Revsnap callback URL

"Admin required" when connecting​

Symptoms: The Connect button is disabled with an "Admin required" label.

Cause: Your workspace role is Member, not Admin.

Fix: Ask a Workspace Admin to connect the org, or request an admin role change.

Token expired or revoked​

Symptoms: Snapshots fail to capture, runs fail with auth errors, org shows unhealthy status.

Fixes:

  1. Disconnect the org from Environments
  2. Reconnect via OAuth to refresh the token
  3. If the issue persists, check whether the Salesforce Connected App is still active

Org shows as unhealthy​

Revsnap periodically checks whether it can reach each connected org. An unhealthy status usually means:

  • The refresh token was revoked in Salesforce
  • The Connected App permissions changed
  • The org is in maintenance or unreachable

Reconnect the org to restore health. If the problem continues, verify API access in Salesforce Setup.

Multiple orgs​

You can connect multiple Salesforce orgs to one workspace (within your plan's org limit). Each snapshot is tied to the org it was captured from: runs always compare against the org associated with the snapshot.