When using the Blob Storage Built-In connector and uploading files saved with UTF-8 with BOM encoding, the connector does not work.
The Azure Blob trigger does not initiate the workflow when files with UTF-8 with BOM encoding are added to the corresponding container. Given that the trigger just does not initiate, but no error is returned, this exception is very hard to troubleshoot.
The Azure Blob read action returns an error when reading files with UTF-8 with BOM encoding. The returned error is:
{
"code": "ServiceProviderActionFailed",
"message": "The service provider action failed with error code 'InternalServerError' and error message 'Unexpected character encountered while parsing value: . Path '', line 0, position 0.'."
}
Given that some editors support this encoding, and that in some cases, this is the default encoding, please add support to this encoding in the connector. It worth noting that the managed blob connector v2 is able to process files with this encoding without any issues.
If adding support for this encoding was not possible, please provide better exception errors, so developers and operators can troubleshoot accordingly. While this is fixed, please update the documentation to state this limitation. Thanks!
Plan Type
Standard
Steps to Reproduce the Bug or Issue
Create a JSON file with UTF-8 with BOM encoding
Create a Storage account and a blob container
Create a Logic App with Blob Storage Built-in trigger and configure the container path accordingly
Upload the JSON file with UTF-8 with BOM encoding to the container
Wait for the workflow to be triggered. No trigger is initiated. No error is returned.
Open the same JSON file and save it as UTF-8 without BOM,
Upload the JSON file with UTF-8 encoding to the container
Wait for the workflow to be triggered. The trigger works as expected.
Furthermore, when uploading more than 10 files with UTF-8 with BOM encoding to the blob container, I faced some responsiveness issues with my Logic App as if the trigger is having issues with the internal exceptions that are not bubbled up and the retry mechanism.
For the action issue:
Create a JSON file with UTF-8 with BOM encoding
Create a Storage account and a blob container
Create a Logic App with recurrent trigger and Blob Storage Built-in read blob action and configure the container path accordingly
Upload the JSON file with UTF-8 with BOM encoding to the container
Run the workflow.
Review the error. This will be as described above.
Upload the JSON file with UTF-8 encoding to the container
Run the workflow. The workflow works as expected.
Workflow JSON
No response
Screenshots or Videos
This is a screenshot for the Read Blob action error when reading a file withUTF-8 with BOM encoding
Describe the Bug
When using the Blob Storage Built-In connector and uploading files saved with
UTF-8 with BOM
encoding, the connector does not work.UTF-8 with BOM
encoding are added to the corresponding container. Given that the trigger just does not initiate, but no error is returned, this exception is very hard to troubleshoot.UTF-8 with BOM
encoding. The returned error is:Given that some editors support this encoding, and that in some cases, this is the default encoding, please add support to this encoding in the connector. It worth noting that the managed blob connector v2 is able to process files with this encoding without any issues.
If adding support for this encoding was not possible, please provide better exception errors, so developers and operators can troubleshoot accordingly. While this is fixed, please update the documentation to state this limitation. Thanks!
Plan Type
Standard
Steps to Reproduce the Bug or Issue
UTF-8 with BOM
encodingUTF-8 with BOM
encoding to the containerUTF-8
without BOM,UTF-8
encoding to the containerFurthermore, when uploading more than 10 files with
UTF-8 with BOM
encoding to the blob container, I faced some responsiveness issues with my Logic App as if the trigger is having issues with the internal exceptions that are not bubbled up and the retry mechanism.For the action issue:
UTF-8 with BOM
encodingUTF-8 with BOM
encoding to the containerUTF-8
encoding to the containerWorkflow JSON
No response
Screenshots or Videos
This is a screenshot for the Read Blob action error when reading a file with
UTF-8 with BOM
encodingAdditional context
No response