How to track issue in such situation

I’m getting data from a Google document and publishing it as an Instagram post. The log seems to be without errors, but I don’t see any result on Instagram. Where should I look to find out what the problem might be? Thanks in advance.

Welcome to the Make community!

This is because the module is a POLLING trigger, and not an INSTANT (Webhook) trigger.

There was nothing new to fetch when the scenario was run, so it did not proceed further.

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.

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.

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

@samliew

1 Like

Welcome to the Make community!

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 rerun your scenario with next using the “Choose manually” option.

For more information, see

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

@samliew

1 Like

Thank you! It is really very detailed and highly relevant explanation!