Skip to content

Commit 14c733c

Browse files
Merge pull request #289270 from xuehongg/mybranch8
Logic App Standard: explain how built-in auto-complete sb trigger works
2 parents ef32849 + 80ab37a commit 14c733c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/connectors/connectors-create-api-servicebus.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 09/03/2024
8+
ms.date: 10/26/2024
99
ms.custom: engagement-fy23
1010
---
1111

@@ -342,7 +342,7 @@ By default, the Service Bus built-in connector is a stateless connector. To run
342342

343343
1. In the designer, [follow these general steps to add the Azure Service Bus built-in trigger that you want](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger).
344344

345-
This example continues with the trigger named **When messages are available in a queue**.
345+
This example continues with the built-in auto-complete trigger named **When messages are available in a queue**. This trigger reads the message from a service bus. If the logic app can get the message and save the trigger response to storage, the trigger automatically completes the message. If a failure happens instead, the trigger abandons the message. These behaviors only apply to stateful workflows. For stateless workflows, the auto-complete or abandon decision happens only after the run completes.
346346

347347
1. If prompted, provide the following information for your connection. When you're done, select **Create**.
348348

0 commit comments

Comments
 (0)