You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From Azure SQL using sp_invoke_external_rest_endpoint a message is successfully queued in Azure Queue. The payload is <QueueMessage><MessageText>HelloWorld</MessageText></QueueMessage>.
When the Queue Triggered Azure function dequeues the message it ultimately lands in the poison queue.
If I take the same message, in this case HelloWorld, and add it via the portal (only works if the "Encode the message body in Base64" is checked), then the message successfully dequeues.
I've tried a variety of things to gain understanding of what is happening in the background, but I've run out of ideas.
This feels like an encoding problem. Any ideas on how best to solve this?
Below is some code if there is a desire to recreate the experience.
SQL Code (Azure SQL Database)
From Azure SQL using
sp_invoke_external_rest_endpoint
a message is successfully queued in Azure Queue. The payload is<QueueMessage><MessageText>HelloWorld</MessageText></QueueMessage>
.When the Queue Triggered Azure function dequeues the message it ultimately lands in the poison queue.
If I take the same message, in this case HelloWorld, and add it via the portal (only works if the "Encode the message body in Base64" is checked), then the message successfully dequeues.
I've tried a variety of things to gain understanding of what is happening in the background, but I've run out of ideas.
This feels like an encoding problem. Any ideas on how best to solve this?
Below is some code if there is a desire to recreate the experience.
SQL Code (Azure SQL Database)
Azure Function App Code
The text was updated successfully, but these errors were encountered: