STAT Deployments failing in some regions #494
Closed
briandelmsft
started this conversation in
General
Replies: 1 comment
-
This issue appears to be resolved with deployments succeeding in all 6 tested regions today. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
STAT deployments of the custom connector started failing recently in some data center regions. We are looking into this but these are not due to any changes on the STAT side.
The top level error you will see is:
The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. Click here for details
when clicking into the failing resource you will see a more detailed error of:
The custom API swagger is not valid: 'Error reading string. Unexpected token: StartObject. Path 'paths['/api/modules/base'].post.parameters[0].schema.default'.'. Click here for details
As of this morning we tested:
East US ✅
West US ✅
East US2 ✅
Central US ❌
Canada Central ❌
North Europe ❌
Australia East ❌
At this time we do not have a workaround other than trying to deploy in other data center regions.
Beta Was this translation helpful? Give feedback.
All reactions