Azure Table Storage
An Azure service that stores structured NoSQL data in the cloud.
170 questions
Intermittent connection failure while connecting to storage account from logic app
![](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(112.00000000000001, 38%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
Abhijit Jadhav (INFOSYS LIMITED)
11
Reputation points Microsoft Vendor
We are connecting to storage account from logic app to save some flags values in storage account table. We are getting below intermittent error with Bad Request Error code in this step. We see, this issue comes several times every month. There are no changes happened in storage account in this particular time whenever below errors are occurred. In this logic app, same storage account is used at two different steps. There are cases where below error didn't come in first step(where this storage account is used) but it came in second step. This means, in a difference of seconds suddenly logic app is facing storage connection issue. This is definitely intermittent and weird.
SA configuration is : storage account is general purpose V2, Replicate is RA-GRS, Performance - Standard, Disk state- both primary and secondary available, location - west central US
Error:
"message": "{\r\n \"path\": \"forward-request\",\r\n \"source\": \"forward-request\",\r\n \"message\": \"The remote name could not be resolved: 'saname.table.core.windows.net'\",\r\n \"reason\": \"BackendConnectionFailure\"\r\n}"
Please help to understand the root cause and solution to fix the issue. Not sure, how such intermittent issues can come so frequently, when availability of azure resources is claimed 99.9 %
{count} vote
-
MayankBargali-MSFT 70,426 Reputation points2022-11-16T10:40:22.283+00:00 @Abhijit Jadhav (INFOSYS LIMITED) Thanks for reaching out. We are discussing the issue offline and will update the thread post our discussion.
-
![](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(150.4, 61%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Sebastian 1 Reputation point2022-11-28T10:41:23.55+00:00 We have the exact same issue at one of our customers.
Logic App uses storage table connector to read a record but intermittently fails with error
"message": "{\r\n \"path\": \"forward-request\",\r\n \"source\": \"forward-request\",\r\n \"message\": \"The remote name could not be resolved: '<tablename>.table.core.windows.net'\",\r\n \"reason\": \"BackendConnectionFailure\"\r\n}"Although this is an intermittent/transient error, a 400 - Bad request status code is returned, preventing the logic app's action default retry to execute.
SA configuration is : storage account is general purpose V2, Replicate is LRS, Performance - Standard, Disk state- available, location - west europe
Metrics show there is almost no load in terms of requests on the storage account around time of failure.Until recently, we have not encountered this issue.
Please investigate this issue.
Sign in to comment
Sign in to answer