The message is processed under the hood and moved to the Dead Letter Queue (DLQ).
No run history is displayed in the Logic App, even though the message was processed.
Test with a different configuration:
Place a similar message on the queue, but leave the Content-Type header empty or remove it.
In this case, the Logic App run history does display the processing correctly.
Expected Behavior:
The Logic App run history should always be visible, regardless of whether the JSON message is malformed or not, as long as the trigger processes the message.
Moving this to the backend issue repo. If this is affecting an production environments for you, I would highly recommend opening a support ticket for quicker responses.
Describe the Bug with repro steps
Bug Report:
"Stateful Logic App Peek Lock Trigger skips run history for malformed JSON messages with Content-Type 'application/json'"
Steps to Reproduce:
Configure the Logic App:
Create a stateful Logic App workflow with the following steps:
Place a message on the queue:
Use a message with the following characteristics:
application/json
.Observe the behavior:
Test with a different configuration:
Place a similar message on the queue, but leave the Content-Type header empty or remove it.
Expected Behavior:
The Logic App run history should always be visible, regardless of whether the JSON message is malformed or not, as long as the trigger processes the message.
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
No response
Browser
Chrome
Additional context
No response