multi-geo capacity workspaces assigned to same workload... load failures

Workload Manifest Schema Version (if relevant)

No response

Your Question

In order to increase our region coverage for our workload, we have configured our manifest to use “WorkspaceRegion” as a ResolutionContextProperty.

With that, we use 4 workloads in the regions US East, US West, Germany West Central, and UK South with geographic boundary mapping to cover 18 fabric revisions (all of continental US, all of EU, and the UK).  To assist with our testing, we have purchased a multi-go capacity in each of our 4 directly supported regions.   For the sake of describing my issue, consider East US and West US.

A test scenario:
Open an asset in a workspace associated with an East US capacity (object type SAS.DecisionBuilder.Decision)
Opens successfully

Immediately open as asset in workspace associated with a West US Capacity (object type is still SAS.DecisionBuilder.Decision)
Fails to open

I think I know what is happening.  Fabric sees the object type is the same as a previously opened asset and assumes it does not need to resolve the endpoint when in truth, the region of the workspace is different for the second open than for the first.

Is there something that we can do to force the endpoint to be resolved again?

Context / Background

No response

Additional References

No response

Reproduce the reported sequence using the manifest's “WorkspaceRegion” ResolutionContextProperty and workspaces on East US and West US capacities, opening the same SAS.DecisionBuilder.Decision asset type in succession. Inspect how endpoint resolution behaves when the workspace region changes; done means identifying a supported way to force resolution again or documenting that this scenario is unsupported.