I am setting up scenario and my trigger is Gmail Watch Emails module.
When I do run once feels like it is random behaviour.
I am aware of the option “Choose where to start” (I see “From now on” as default) but when I save for example “All Emails” and then click again on “Choose where to start” I see “From now on” again.
So where does it reset? what is behaviour here? I am not sure what am I running once on?
Hi @Won_t_Tell
When you pick “Choose where to start” in the Gmail Watch Emails module and select something like “All Emails”, that choice is only used once — the very first time you run the scenario after saving it. That is When you select “All Emails”, you have to run the module to list all the mails . Instead if you open choose from where to start again, It will show from now and if you save and then run the module it will not fetch all mails.
After that first run, Make keeps track of the last email it processed. So the next time it runs, it starts from that point, not from “All Emails” again.
Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation
This is because the Watch Emails 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.
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), see if your app has an “Instant” or “Webhook” trigger in Make. If not, check if the third-party service has a feature that can send out a webhook when content is created/updated - and then you can point it to a “Custom Webhook” trigger in your scenario.
If you want to re-run your scenario on 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
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
