Overwriting of automations

User Talk Automations
1

Hey,

in the Cloud Version, I very often face the issue, that an automation gets overwritten by another automation, after I change something. This happens very often, when you are working quick and open some automations for just a short moment.

For example, I have an Automation “A” and “B”, I want to change the Automation “B” for some reason, and then I suddenly have listet two Automations “B” “B” and no more “A”.

Of course, after that the hole base does no longer work, because one automation is missing.

There should be at least some kind of warning before an automation gets over written.

2

I’m not fully understand your issue from the description. Can you paste a screenshot? This can help a lot.

3

I just created a test base for this, containing three automations, Automation C is a periodic automation:

grafik
grafik342×310 2.66 KB

Automation A - It will change the date for new data sets:

grafik
grafik831×870 8.77 KB

Automation B - once the date is set it will change the value to 5€:

grafik
grafik832×874 10.9 KB

Automation C - This is a periodic automation setting the single select to Ja:

grafik
grafik826×870 17.9 KB

Once they are created and I start to click into the automation and change things or just click into the automation and do not change things, it happens sometimes that one automations gets overwritten.

Now I have two Automation A (both are identical!!), one Automation C and Automation B is gone/overwritten:

grafik
grafik344×312 1.99 KB

New Automation A (1) - It sets the date for new data sets:

grafik
grafik818×863 9.3 KB

New Automation A (2) - also sets the date for new data sets:

grafik
grafik828×871 9.39 KB

New Automation C - sets the value for the single select to Ja:

grafik
grafik831×868 17.9 KB

So this base will no longer change the value to 8€ for the new datasets, as soon as the date is set.

I assume the issue has something to do with the periodic automation function, because it happens as soon as you have them set.

4

Can you confirm, that this is your main problem, right?

I tried to recreate this problem for about half an hour and the automations were never overwritten or changes, without my doing. Can you reproduce this behaviour at https://cloud.seatable.io?

5

Yes, this is a problem we have in our office using the bases.

It is important that the automation you change and save to overwrite already existing automations has to be an periodic automation.

6

Sorry, but I don’t get it. Can you reproduce the behaviour at …

7

We are using Cloud. This behaviour occurs in various bases, when periodic automations are involved.