Azure / Azure/azure-rest-api-specs
[LogicApp] Throws RequestFailedException exception, but actually creates successfully
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 424
Description
- Request Path: /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Logic/integrationServiceEnvironments/{integrationServiceEnvironmentName}
- Operation Id: IntegrationServiceEnvironments_CreateOrUpdate
After calling the `IntegrationServiceEnvironments_CreateOrUpdate` method and waiting for the deployment to finish, the API will return the following error, but the resource is actually created and can be obtained through the REST API Get method
#### RestApi return
``` log
Azure.RequestFailedException: Encountered internal server error. The tracking Id is '*******-*********-*******-********'.
Status: 200 (OK)
ErrorCode: InternalServerError
```
#### Portal operation log
``` log
{
"status": "Failed",
"error": {
"code": "ResourceOperationFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "InternalServerError",
"message": "Encountered internal server error. The tracking Id is '******-******-*****-*****-******'."
}
]
}
}
```
Contributor guide
Research direction
Start with the IntegrationServiceEnvironments_CreateOrUpdate operation at the stated request path and compare its completion response with the REST API Get method. Review the reported RequestFailedException, portal operation log, and Status: 200 response to determine whether the specification or service behavior is incorrect. Done means the successful creation no longer produces a contradictory failure, or the API contract clearly reflects the actual result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100