Skip to main content

I have built a system where various tables for different Internal departments sync to a “target” table where an API takes the data and uses it in a Warehouse management system. The idea is to use this target table as a place where everything is put together, ideally without any human intervention.

However now I've just read the following in the sync support section:


Automatic syncs will eventually stop on bases that don't have any recent activity. To keep automatic syncs active make sure that some kind of action (i.e. create a record, update a record, create a new view, etc.) is being performed in the base on a regular basis by automations, humans, or a combination of the two.

 

I wonder how that will affect my target table in the long run.

  • Do new rows that are created via the sync count as 'created record' even though there is no human intervention in the target table?
  • The use of this table is periodic, as the nature of my business is seasonal. So to avoid any sync to stop working, will a periodically run automation, say a weekly automation will click a check box. Will that be enough to keep the sync running? 
  • It says the automatic sync will eventually stop being active. Does anyone know what time horizon this is? weeks, months,  half a year?

Hey ​@Kim_Trager1,

 

Yes in my experience that would be more than enough! 

Do new rows that are created via the sync count as 'created record' even though there is no human intervention in the target table?

I don’t think so, I vaguely remember having this exact issue of a synced table not picking up a new record because that base was untouched

---

The use of this table is periodic, as the nature of my business is seasonal. So to avoid any sync to stop working, will a periodically run automation, say a weekly automation will click a check box. Will that be enough to keep the sync running?

Yeap it would.  Your workflow’s okay with working with one week old data?

---

It says the automatic sync will eventually stop being active. Does anyone know what time horizon this is? weeks, months,  half a year?

I think it was a couple of days / weeks for me

No, creating records via sync is not treated as a user activity. So, you'll likely need to set up an automation to keep the base active.

I've seen bases go inactive within a couple of hours as well. Airtable doesn't clearly define the exact timeframe for inactivity, so you may need to experiment. Start by checking after 2 hours, then gradually double the interval to see how long the base stays active.

A better option might be to reach out to Airtable support for an accurate timeframe regarding base inactivity.

I've also written an article on this topic, which you can read here.

Taha, Airtable Advisor

Hi ​@Kim_Trager1,

Bases “fall asleep” multiple times per day, and they fall asleep in a relatively short amount of time. They will fall asleep in just an hour or so after they’re not being actively used.

So the solution is that you’ll need to wake up BOTH the source base AND the destination base whenever you want the sync to happen.

And you’ll want to make sure that you wake up the source base about 10 minutes before the destination base.

The easiest way to do this would be to set a scheduled automation in each base that runs on a schedule, such as once a day or once a week or whenever you need the sync to happen.

Hope this helps! If you’d like to hire an expert Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Thanks ​@Mike_AutomaticN , ​@TheTimeSavingCo and ​@ScottWorld for these inputs.

 

​@TheTimeSavingCo, The idea would then, I guess, be a daily or twice-daily scheduled automation.

 

​@ScottWorld Do you know if a Make automation would also count as an automation, or would it need to be a native Airtable one?

 

Yes, I believe that a Make automation will wake up the bases as well.

- ScottWorld, Expert Airtable Consultant

Terms & ConditionsAccessibility statement