Polling Triggers & Empty “Check Runs”
This is because the module is a POLLING trigger, and not an INSTANT (Webhook) trigger.
If you don’t see any bundles from the trigger module and operations on the rest of the modules, it means there are no new responses (empty output bundle) when the scenario ran to check for new items. This is called a “Check run”.
There are two main types of triggers, Polling (scheduled), and Instant (webhooks). Polling triggers can only run on a schedule. Instant triggers can be run as soon as data is received by the webhook.
- Polling means Make checks external service for changes (pull changes to Make).
- Webhook (instant) triggers means external service calls Make when there are new changes (push changes to Make).
The module you are using does not push changes — it’s basically a API request that Make has to occasionally “call” to fetch the latest changes/items.
To find out more on the different types of Trigger modules, see refer to Types of Modules and Webhooks sections of the Make Help Centre.
If you want your scenario to only run when there is new data (and not on a schedule or timed interval), you can use the “Custom Mailhook” module instead.
If you want to re-run your scenario on older data,
Polling Triggers: Epoch Panel & Selecting Older Data
Go to the Epoch Panel, by right-clicking on the trigger module (polling triggers only), and select “Choose where to start” from the list of options in the context menu.
If you select “From now on”, the next time the scenario runs it will only return new data (or nothing if there is no new data).
You can also select other old data to re-run your scenario with next using the “Choose manually” option. This will then show you a list of previous historical items you can select to process the next time the scenario is triggered.
For more information, see
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
