The "azurefile" connector action "Create_file" failed xx times with status "Conflict"

Bert van Dijk 0 Reputation points
2024-03-18T15:40:31.2366667+00:00

Since the beginning of March we get errors in a logic app, when creating a file.

The "azurefile" connector action "Create_file" failed 10 times with status "Conflict" between 3/14/2024 9:31:33 PM and 3/14/2024 9:36:34 PM.

Error code 409

Error: The specified resource may be in use by an SMB client.

The only documentation I can find on this issue is when you try to modify or delete a file, not on the creation.
What could be the cause of this error on the creation step?

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,213 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,964 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sumarigo-MSFT 44,996 Reputation points Microsoft Employee
    2024-03-19T07:55:02.7033333+00:00

    @Bert van Dijk Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    Based on the error message: The specified resource may be in use by an SMB client. While creating a file with the Azure File Storage connector in a Logic App, but unfortunately, This error code typically indicates a conflict, such as when a resource is already in use or locked by another process, which can happen even during creation if the file name already exists or is being accessed simultaneously by another client. Without specific documentation, it's challenging to provide a definitive cause for this error during the creation step. It may be beneficial to check if the file name being created already exists or if there are any locks on the file share that could be causing this conflict.

    • If the file is not in use by an SMB client, try creating the file again. If the error persists, you can try creating the file with a different name or in a different directory.
    • If multiple instances of the logic app are running simultaneously or multiple logic apps are trying to create files concurrently, it could lead to conflicts. Check if there's a spike in activity or if multiple instances of the logic app are being triggered concurrently.
    • Implement some form of synchronization or throttling mechanism to ensure that only one instance of the logic app is creating files at a time.
    • Verify that the credentials used in the "azurefile" connector action have the necessary permissions to create files in the target directory of the Azure file share.
    • Review the configuration of your logic app, including any parameters or settings related to the "azurefile" connector action. Double-check the configuration of the "azurefile" connector action to ensure that it's pointing to the correct Azure file share and directory.

    Additional information: Please refer to this SO thread, which provide more information on your issue.

    After attempting the aforementioned suggestions and if the issue persists, I would like to work offline on this issue.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.