Replication Tasks and Peeklock : Unable to peek messages for Dead-letter the message/Abandon the message/Complete the message actions from one servicebus queue to other queue dead-letter.

[vgouth]

Describe the Bug with repro steps

Prerequisites:
Create a service bus namespace with two queues.
Create an event hub instance with two hubs.

1.Create a new Stateless logic app in standard, open the designer.
2.Add a service bus "When messages are available in a queue (peek-lock)" trigger.
3.In the trigger, enter the queue name of your first service bus queue in "Queue name". In the trigger settings disable Split On.
4. Add a For each action and select Messages from the dynamic content as its input parameter.
5. Within the for each loop add the action "Dead-letter the message/Abandon the message" from service bus. In the Message ID field select "Message ID" from the dynamic content popup.
6. Save the workflow.
7. Open the service bus queue attached to your trigger and then open the service bus explorer. Create a test message of content type text and send it to that queue.
8. Open the service bus queue attached to your replicate messages action and then open the service bus explorer. Open the peek tab, select the DeadLetter queue and click "peek".

Expected: After clicking peek you should see your message displayed below. Open it and verify that the contents match what you sent earlier.

Actual: Unable to peek messages for Dead-letter the message/Abandon the message actions from one servicebus queue to other queue dead-letter.

What type of Logic App Is this happening in?

Standard (Portal)

Are you using Preview Designer or GA Designer

Preview

Workflow JSON

No response

Screenshots or Videos

Browser

Edge

Additional context

Environment Details:

URL: https://aka.ms/emastaging-flowstip1
Version: 2.30508.1.2

AB#24283754

AB#24494142

[vgouth]

Issue repro after updated and deployed in staging,

Environment Details:
URL: https://aka.ms/emastaging
Version: 2.30529.1.3

Adding a point about the issue: As per the test script, we are not able to peek the messages into different service bus queue like sending the text message from one service bus and peeking the text message into other service bus. But if we try to peek the message in the same service bus like sending the text message and trying to peek the message in the same service bus we are able to peek it. Is there any need in updating the script or else it is a bug ? Attaching the Screenshot of the test case scenario and test suite URL as well.

Test Suite URL : https://msazure.visualstudio.com/One/_testPlans/execute?planId=9712199&suiteId=24117340

[vgouth]

Issue repro in the latest request

Environment Details:
URL: https://aka.ms/emastaging-flowstip1
Version: "2.30613.1.2"

Adding a point about the issue: As per the test script, we are not able to peek the messages into different service bus queue like sending the text message from one service bus and peeking the text message into other service bus. But if we try to peek the message in the same service bus like sending the text message and trying to peek the message in the same service bus we are able to peek it. Is there any need in updating the script or else it is a bug ? Attaching the Screenshot of the test case scenario and test suite URL as well.

Test Suite URL : https://msazure.visualstudio.com/One/_testPlans/execute?planId=9712199&suiteId=24269984

[vgouth]

Issue repro in the latest request

Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30701.1.1

[hartra344]

Migrating, this appears to be a backend issue

[vgouth]

Issue repro in the latest request,

Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30717.1.1

[vgouth]

Issue repro in the latest request

Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30731.1.4

[vgouth]

Issue repro in the latest request

Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30814.1.1

[vgouth]

@AbodeSaafan As this issue is migrated to be a backend issue, requesting you to have a look into it.

Issue repro in the latest request
Environmental Details:
URL: https://aka.ms/emastagiLong-flowstip1
Version: 2.30828.1.2

[AbodeSaafan]

@vgouth can you check with Aprana on this since it's service bus to confirm if this is a bug or incorrect configuration

[vgouth]

@apranaseth Requesting you to have a look into this issue and let us know if this is a bug or incorrect configuration or changes to be done in test case..

[apranaseth]

@vgouth can you reach out to Alex Karcher for replication task question.

[vgouth]

@apranaseth . Thank you for your suggestion.

@alexkarcher-msft Requesting you to have a look into this issue and confirm us if this is a bug or incorrect configuration or changes to be done in test case.

[alexkarcher-msft]

Hi @vgouth . Can you share a screenshot and your workflow.json for the workflow that is driving this behavior? I'd like to see whether any actions are failing and see what queues are being targeted by that workflow.

[vgouth]

Hi @alexkarcher-msft, please find the attached workflow. Json code. All the screenshots are attached above including the test case, the issue one as well.

{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"actions": {
"For_each": {
"type": "Foreach",
"foreach": "@triggerBody()",
"actions": {
"Complete_the_message": {
"type": "ServiceProvider",
"inputs": {
"parameters": {
"messageId": "@Items('For_each')?['messageId']"
},
"serviceProviderConfiguration": {
"connectionName": "serviceBus",
"operationId": "completeMessage",
"serviceProviderId": "/serviceProviders/serviceBus"
}
}
}
},
"runAfter": {}
}
},
"contentVersion": "1.0.0.0",
"outputs": {},
"triggers": {
"When_messages_are_available_in_a_queue_(peek-lock)": {
"type": "ServiceProvider",
"inputs": {
"parameters": {
"queueName": "test3",
"isSessionsEnabled": false
},
"serviceProviderConfiguration": {
"connectionName": "serviceBus",
"operationId": "peekLockQueueMessages",
"serviceProviderId": "/serviceProviders/serviceBus"
}
}
}
}
},
"connectionReferences": {
"serviceBus": {
"connection": {
"id": "/serviceProviders/serviceBus/connections/serviceBus"
},
"connectionName": "abc",
"api": {
"id": "/serviceProviders/serviceBus"
}
}
},
"parameters": {}
}

[vgouth]

@alexkarcher-msft . Thank you for quick connect. As per the updated the test case the issue is not repro, As of now closing this bug.