My scenario stops running after few seconds

[Valery_Ramirez]

What is your goal?

To run an scenario forever until a mail is reached

What is the problem?

Hi all, how are you?.

I have a test scenario where I have linked an yahoo mail account, I think I’ve configured the module to activate it where a mail with a specific subject is received but, whererver the mail is received or not, the run stops about 10 or 15 seconds after the run is initiated. I’ll attach a screen capture to see what can be done to solve the problem.

Thanks in advance for the help

What have you tried so far?

I tried to find the answer to my question but I couldn’t.

Screenshots: scenario setup, module configuration, errors

[Stoyan_Vatov]

Hey Valery,

you are looking for the Custom Mailhook module. That one will trigger instantly when a new email is received.

[Karmic]

If you prefer to use your “Watch Emails” module:

1. Keep your current trigger.

2. Turn the scenario ON.

3. In the Scheduling tab, set it to run every X minutes (for example every 1 or 5 minutes).

Note: Do not rely on “Run once” for your normal operation because it’s basically for “testing” purposes. This strategy will enable your scenario to automatically run on your specified schedule, check for new emails matching your criteria, then stop until the next scheduled time.

Let me know how it goes!

[samliew]

Welcome to the Make community!

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), 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,

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

• Types of Triggers
• Selecting the First Bundle

Hope this helps! If you are still having trouble, please provide more details.

— @samliew
_{P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!}