Help

Airtable automations and Backend performance extremely slow

Topic Labels: Automations
Solved
Jump to Solution
923 1
cancel
Showing results for 
Search instead for 
Did you mean: 
automatery
4 - Data Explorer
4 - Data Explorer

As of today, our airtable automations that react to action triggers of certain fields in not really large tables are incredibly slow and sometimes freeze, so we have to disable and re-enable the automation.
In addition, navigation in the backend is tedious and slow.

Our tables have a very manageable size, the largest tables have around 1500 rows.

Since we also use Softr as a UI, we also notice very poor performance here.
What can we do?

Edit: To make the severity a little bit clearer: Action Trigger was set at 2:54 pm and the automation was finished on 3:49pm! It simple copies a row from Table A to Table B! 

1 Solution

Accepted Solutions
automatery
4 - Data Explorer
4 - Data Explorer

Our issues were caused by the incident below.

To be honest, we find it a little embarrassing that it took a whole working day for this problem to be recognized as a problem in the first place.

Sep 2, 2024
Small percentage of bases experiencing slow loading
Resolved - This incident has been resolved.
Sep 2, 15:53 UTC
Identified - We are aware of an issue that is causing slow loading and other issues with a very small percentage of bases. Our engineers have identified the root cause of the issue and are working on a remediation.
Sep 2, 15:20 UTC

See Solution in Thread

1 Reply 1
automatery
4 - Data Explorer
4 - Data Explorer

Our issues were caused by the incident below.

To be honest, we find it a little embarrassing that it took a whole working day for this problem to be recognized as a problem in the first place.

Sep 2, 2024
Small percentage of bases experiencing slow loading
Resolved - This incident has been resolved.
Sep 2, 15:53 UTC
Identified - We are aware of an issue that is causing slow loading and other issues with a very small percentage of bases. Our engineers have identified the root cause of the issue and are working on a remediation.
Sep 2, 15:20 UTC