Scenario only run 1 time and then data is empty

[Jos]

What are you trying to achieve?

I try to setup a automation for creating database entries in notion but somehow i have a weird issue when i start i choose for item 1 - Watch database items and then from there i build my automation.

The first time i add the “database item” and i do “run once” it shows perfectly all data in it and also the automation runs smoothly.

ATM the first time when i build the scenario everything goes well. But after the first time (so from 2nd time and forward) i press the run once button it seems like the current database is empty and stop loading the data in in and it shows a weird 1 on top and i can not test any further things cause the run once button not run the process anymore and keep giving me the “1”. When i keep pushing the run once button it sometimes loads maybe 40% more but then it stops again without any error notice. So somehow it only runs 1 time my process and then it stops.

If i remake everything again it works 1 time and then i get the same issue over and over again.

Steps taken so far

1. Select APP - Notion
2. Connect database
3. Apply on all
4. Run 1 time
5. Works perfect also the automation works perfect
6. From second try the operation data seems missing in step 1.

Screenshots: scenario setup, module configuration, errors

[samliew]

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 operations after the trigger module, 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

• Polling triggers
• Selecting the first bundle

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

---

P.S.: Did you know, the concepts of about 70% of questions asked on this forum are already covered in the Make Academy. Investing some effort into it will save you lots of time and frustration using Make later!

[Jos]

Thank you very much!