Sandbox Refresh

GRAX Application connections are impacted each time a Salesforce sandbox refresh takes place, however, getting GRAX up and running again in the new environment is a straightforward process.

Why would a Sandbox get refreshed?

  • To bring down a clean copy of the production environment to allow you to start the next project/test with a fresh and updated environment

  • To start a new sandbox due to expiration of previous sandbox

  • May be required as part of a software development cycle

Please note that your sandbox will have a new org ID after the refresh.

GRAX Sandbox Deployment Policy

Like Salesforce, GRAX monitors sandbox deployments for activity and automatically deletes deployments after a period of 180 days of inactivity. This improves security by cleaning up data, and cost by turning off unused servers. At any time you can deploy a new sandbox backend via GRAX Platform or by contacting GRAX Support.

Pre-Refresh Requirements

Before the refresh:

  • Ensure that the Admin Email Address is set to one or more valid email addresses within the Settings section of the GRAX Application

  • Disconnect Salesforce by Resetting GRAX

    • Navigate to Settings

    • Expand the Salesforce panel

    • Click Reset GRAX

Destroy the Current Salesforce Connection

Post-Refresh Reconfiguration

GRAX Application Reconfiguration

  • Login to your sandbox in SFDC as the GRAX Integration user

  • Navigate to your GRAX App at [your-grax-domain-and-port]/web and follow the steps to Connect Salesforce

    • Follow the prompts to Connect with Auto Config and restart Auto Backup

  • Navigate to Settings within the GRAX Application and expand the Salesforce section to confirm that the you are connected to the correct SFDC org with the correct Integration User. You will see a green dot followed by the word Connected if the connection is successful. If you need to modify the connection details, click Update to reset the connection

GRAX Managed Package Reconfiguration

The GRAX Managed Package is optional and not all customers use it. If your organization uses the Managed Package, follow the steps below:

Last updated

Was this helpful?