For a couple of releases now we’ve seen that creating Salesforce Scratch Orgs
on a preview release has been throwing us errors. During this last release window though it now seems we at least no what the issue is.
But first a bit of background. Salesforce provide three major releases a year (Winter, Spring, and Summer), and they provide the ability to get preview access to these for customers and partners so they can test their organisations and implementations prior to the release being rolled out to production. This preview access includes Pre-release sandboxes, and once normal sandoxes rollover (usually ~ 1 month before production) then you can also create scratch orgs on the preview release also.
For our work at Caddify, where we have a no-code tool for building mobile Companion Apps, access to these pre-release and preview orgs is a key part of our process to ensure that our product and apps will work as expected on any upcoming Salesforce release. As I have said though for the last two releases the SFDX CLI commands used to create these preview scratch orgs have been failing, specifically with this error;
ERROR running force:org:create: The request to create a scratch org failed with error code: VR-0003.
I was getting this regardless of whether or not I used a CLI flag to request the org or if I used the config file to define the “Preview” state.
Following on from initial conversations with the folk behind the SFDX CLI it seems that the issue lay somewhere internal to Salesforce processes, and after a helpful dialog with Salesforce support the issue was resolved. It seems that some “internal Instance Mapping table” was missing entries. SF support have now added these and my Preview scratch instances are working.
We have added UMEA instances in Spring’23 to Scratch/Sign-Up routing internally our internal Instance Mapping table
I hope knowledge of this issue, and the cause and cure, will be helpful to others who might run into this.