Sandbox environment

We provide a sandbox environment allowing you to test new features without the risk of overwriting business-critical production data. Our sandbox environment is a mirrored copy of our production environment – both code-wise and database-wise. This way, we guarantee that you get timely access to all newly released features and you can work with your own database that you're familiar with.

FAQs

Why do we reset the sandbox environment every two weeks?

We keep the sandbox data up to date with our production data which is the source of truth. Sandbox data is only temporary so by enforcing a reset every 2 weeks, we can be confident that the sandbox data stays up-to-date and closely matches our production environment.

Can we do a custom reset outside of the schedule or for a single client?

Unfortunately, we cannot facilitate that.

How long does it take for the sandbox to be operational again?

Usually, it takes about an hour or two to be operational again. To be sure your workflows are not impacted, consider that it can take up to 24 hours to reset the sandbox data, transfer over the production data and re-index it on sandbox. During this period, the sandbox environment may not be accessible or data may not appear in the platform or be returned in the API.

Where can I find information about the current status of the Sandbox?

The current status and any logged changes and instances of all our systems can be checked and found here: status.uberall.com

Can I also test the Uberall platform in the Sandbox environment?

Yes - our platform is also supporting a Sandbox version. Simply login via sandbox.uberall.com/login, using your standard login credentials.

Reset dates

For your convenience, find the dates when the sandbox environment is reset.