This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 34%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
I created an Azure API Management instance (Standard v2) via Terraform. During terraform apply the instance should have been destroyed and recreated. It seems like this has gone wrong. Further terraform apply lead to status 409 Conflict. The service already exists.
Status right now is: I can not create an API Management instance with the name I used previously - but I need to. When I check the Portal, I don't see this particular resource. When I check for deleted resources via API it shows an API Management instance with the name with a suffix.
When I try to purge this resource (via API), it says: "Service locked. The API Service XXX is transitioning at this time. Please try the request again later."
What can I do to unlock this? I already waited 1,5 h to see, if it unlocks somewhen. This did not happen.
If someone working for Microsoft is able to check: Name of the resource is pk-apimgmt-echt
Thanks in advance.
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 59%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
@Andreas Rehmann Thanks for reaching out. If the service is undergoing a service level operation, we lock the service, and any other similar service level operation initiated by the customer while the previous one is running will result in a 409 response code with an exception
{"error":{"code":"ServiceLocked","message":"The API Service pk-apimgmt-echt is transitioning at this time. Please try the request again later.","details":null,"innerError":null}}
This occurs because the previous operation was still in progress. Could you please retry and confirm if you were able to purge the service successfully now?
Answer accepted by question author
@Andreas Rehmann Thanks for your patience! I had initiated a request from backend to clean up the resource and it's successful now. Please try to recreate the service with the same name and that should be successful.
do let me know incase of further queries, I would be happy to assist you.
Thank you very much for your kind support. It works now.