@PS Thanks for reaching out. I can see the path as ContainerName/abc/abc1/abc2/{queueTrigger} so it means that whatever the message content is send it will use the same name while creating the blob. So in scenario when the message is simple text then the blob name will be created successfully but let's say you are passing JSON body to your queue message then this json body will be invalid as the blob name and output binding will fail. The suggestion would be change the blob name to randguid or any random name which is valid blob name.
{
"bindings": [
{
"name": "myQueueItem",
"type": "queueTrigger",
"direction": "in",
"queueName": "outqueue",
"connection": "AzureWebJobsStorage"
},
{
"name": "ContainerLandingOutput",
"type": "blob",
"path": "ContainerName/abc/abc1/abc2/{rand-guid}",
"connection": "AzureWebJobsStorage_EDW",
"direction": "out"
}
],
"disabled": false
}
The above will create random blobs and the blob file will have the actual message content.
Feel free to get back to me if you have any queries or concerns.
Please accept as "Yes" if the answer is helpful so that it can help others in the community. If you need any help/clarification/concerns/follow up questions, then please click on "Add Comment" on my answer and provide more details.