Network traffic is not blocked from the current tenant to the connected tenant. This could happen if the user’s Identity Profile blocks access or if the Network Setting does not allow traffic from the target tenant.
Tenants should be in the same region.
Check the PAT (scope) is correct as per documentation. Also, the clientID and clientSecret entered is correct. [This is the details of Sandbox]
Now, check the orgName (Admin → Dashboard → overview → orgdetails) and the tenant name you entered are correct.
It’s connected now—I tested with two partner tenants successfully. I believe the previous issue was due to a network or firewall restriction. Thanks for your response!
However, I’m now trying to draft the source from the target tenant into the current tenant, but I’m encountering an error even though I’ve verified that the source exists in the target environment.
This might be due to the reference found in the Source tenant and target tenant might differ.
Lets say for example - In the connected tenant, there might be a source owner data. Which has different id/name. This data might needs to be changed as per the data in live tenant.
This can be done via two ways -
By adding the Object Mappings (This will be applied once the draft is created from backup).
I have added the identity mapping for owner of the source. you can find the difference below
Before adding the identity mappings
“errors”: [ { “key”: “SOURCE_IMPORT_FAILED”, “text”: “An error occurred importing source: ‘Source_123’”, “detail”: { “exceptionMessage”: “Identity with ID or name jack123 was not found.” } } ],