Closed lilan123 closed 2 months ago
did you get any workaround for this issue?
@RichaKapoor7 As of now, the workaround that we implemented is to change the run after setting as below.
Thanks for your reply. But message still remains in queue as deferred. Why this is happening at first place?
On Thu, 30 May, 2024, 07:57 Lilan Sameera, @.***> wrote:
@RichaKapoor7 https://github.com/RichaKapoor7 As of now, the workaround that we implemented is to change the run after setting as below. image.png (view on web) https://github.com/Azure/logicapps/assets/7977013/a18ffad0-b920-4512-ac0f-7e9441285315
— Reply to this email directly, view it on GitHub https://github.com/Azure/logicapps/issues/1049#issuecomment-2138812476, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGBJH2RENQOZWHH2ONOFFHTZE3EW7AVCNFSM6AAAAABG5LZGDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYHAYTENBXGY . You are receiving this because you were mentioned.Message ID: @.***>
We have the same issue when completing/dead-lettering a message. Granted, it happens whilst our app service plan is scaling outwards, so the error message is correct. However - why does this happen? Why is Service Bus the only connector I've encountered that does not work well when scaling outwards?
This issue is stale because it has been open for 45 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Describe the Bug
ServiceBus built-in Defer message shows inconsistent behaviour when running to defer a message on the ServiceBus topic. Sometimes, it successfully defers the message; other times, it fails with a bad request result, as below. However, when checking the service bus topic, the message shows the deferred state.
NB: Action trigger Times
Plan Type
Standard
Steps to Reproduce the Bug or Issue
Workflow JSON
Screenshots or Videos
Additional context
No response