{"id":110880,"date":"2017-08-01T07:40:14","date_gmt":"2017-08-01T14:40:14","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/four-connector-action-settings\/"},"modified":"2025-06-11T08:12:33","modified_gmt":"2025-06-11T15:12:33","slug":"four-connector-action-settings","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/four-connector-action-settings\/","title":{"rendered":"More action settings and four new connectors"},"content":{"rendered":"

New action and trigger settings<\/h2>\n

Flow now gives advanced users more control over how their triggers and actions run. For triggers there are three new settings. You can access these settings by selecting the …<\/strong> menu at the top-right of the trigger and then choosing Settings<\/strong> from the menu:<\/p>\n

<\/p>\n

The first setting is Split On<\/strong>. Split on makes it so that each item in list of items, such as Tweets or Emails, gets its own flow run. For example, if a trigger checks for tweets every 5 minutes, and there are twenty tweets in that period of time, the flow will run twenty times. This is the default behavior. However, if you want to work with all twenty tweets at once, you can now disable Split On, which means you will have only one run, but with a list of tweets.<\/p>\n

The second setting is\u00a0Retry policy<\/strong>. You can configure how many times the flow will retry when there is a transient failure. The default is four times, but you can adjust this or turn off retries entirely.<\/p>\n

The final setting is\u00a0Single instance<\/strong>. Use single instance if only want one run to happen at a time.\u00a0<\/p>\n

There is one additional setting specific to actions (in addition to Timeout, which we shared previously<\/a>, and Retry policy<\/strong>, from above): Pagination<\/strong>. Pagination enables you to handle more records than are returned in a single call from a service. For example, some services only return back 50 items at a time. However, in the flow, you may want to get all of the items in the list. By turning on pagination, the flow engine will continue to call the service until it has all of the items – or – hits the limit that you explicitly define in the flow.<\/p>\n

\"\"<\/p>\n

Four new connectors<\/h2>\n

We have released four new connectors in the past week:<\/p>\n