Skip to content

Commit eec1541

Browse files
authored
Acrolinx fix
1 parent e332f12 commit eec1541

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/logic-apps/logic-apps-pricing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ To help you estimate more accurate consumption costs, review these tips:
7171

7272
* Consider the possible number of messages or events that might arrive on any given day, rather than base your calculations on only the polling interval.
7373

74-
* When an event or message meets the trigger criteria, many triggers immediately try to read any other waiting events or messages that meet the criteria. This behavior means that even when you select a longer polling interval, the trigger fires based on the number of waiting events or messages that qualify for starting workflows. Triggers that follow this behavior include Azure Service Bus and Azure Event Hub.
74+
* When an event or message meets the trigger criteria, many triggers immediately try to read any other waiting events or messages that meet the criteria. This behavior means that even when you select a longer polling interval, the trigger fires based on the number of waiting events or messages that qualify for starting workflows. Triggers that follow this behavior include Azure Service Bus and Azure Event Hubs.
7575

7676
For example, suppose you set up trigger that checks an endpoint every day. When the trigger checks the endpoint and finds 15 events that meet the criteria, the trigger fires and runs the corresponding workflow 15 times. The Logic Apps service meters all the actions that those 15 workflows perform, including the trigger requests.
7777

0 commit comments

Comments
 (0)