Scenario runs successfully but Google Sheet is not updated (only in automatic mode)

Hi everyone,

I’m facing an issue with my scenario that updates a Google Sheet daily from a CSV file received by email.

  • When I run the scenario manually, everything works perfectly: the CSV is processed and my Google Sheet is updated as expected.

  • When the scenario runs automatically (scheduled once a day), Make shows the execution as successful (no errors in the history, status “success”, no incomplete execution), but the Google Sheet is not updated at all.

The scenario had been working perfectly for 2 months. About a week ago, it suddenly stopped updating the Sheet automatically. I did review the scenario in detail around that time, but I did not modify any step.

Has anyone experienced something similar, or do you know what might cause this behavior?

Thanks a lot for your help!

example of an automatic run that is said successful on Make (but no refreshed data in my gsheet)

scenario.blueprint.json (26.0 KB)

We’d love to help, however, you have not provided sufficient information to demonstrate the problem that would allow us to reproduce the scenario and any issue/s and/or error/s.

To allow others to assist you with your scenario, please provide the following:

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are extremely important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

  • the full scenario,
  • any error messages,
  • individual module fields,
  • relevant filter settings (conditions), and
  • each module’s output bundles
  • any external services (spreadsheet headers, sample data, regex101.com, etc.)

You can upload images here using the Upload icon in the text editor:

We would appreciate it if you could upload screenshots here instead of linking to them outside of the forum. This allows us to zoom in on the image when clicked, and avoid tracking cookies from third-party websites.

2. Scenario Blueprint

Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!

To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.

You can upload the file here by clicking on this button:

3. Module Output Bundles

Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).

Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.

You can upload the file here by clicking on this button:

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.
Here are some ways to provide text content in a way that it won’t be modified by the forum.

  • Method 1: Type code fence manually
    Add three backticks ``` in a separate line before and after the content, like this,

    ```
    text goes here
    ```
    
  • Method 2: Highlight and click the “preformatted text” button in the editor

  • Method 3: Upload your file and share the public link
    (this method is only recommended for large files exceeding the forum upload limit)

Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.

Sharing these details will make it easier for others to assist you.

I noticed something strange when looking at the execution history.
For example, on September 21, the scenario ran at 22:15 as scheduled. However, the attachment processed by the scenario was the CSV from September 19, not the one received on September 21.

Here’s the setup:

  • I receive an email with a CSV attachment every day at 22:00 (always from the same sender).

  • The scenario is scheduled to run at 22:15 to fetch the latest CSV from that sender.

  • Instead of picking the CSV from the same day, the scenario sometimes processes an older attachment (e.g., on Sep 21 it used the Sep 19 file instead of the Sep 21 file).

So it seems the issue is not with the update of the Google Sheet itself, but with the retrieval of the correct attachment in automatic mode.

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

Thanks a lot! it works properly now!

“From now on” was already selected but maybe needed to be reselected again