I have one particular action whose column edit always takes a very long time to process. All the action itself does is toggle a boolean value in a single row in order to trigger an automation (to send an email). Other actions that toggle boolean values in other columns in the same table never take so long, including when I test them from the same view showing the same row. Does anyone have guidance for how to troubleshoot?
Outlier action: Always takes a long time
Typical action: Never takes anywhere near as long
Solved! Go to Solution.
I think it was the email task triggered by the row edit, not the row edit per se.
The Email Body property had multiple SNAPSHOT expressions. When I removed those, performance really picked up, and it seems to be working pretty snappy now. FYI, even commenting out the SNAPSHOT expressions didn't make a difference.
I guess the row edit action was just waiting on the end-of-automation sync before completing. I don't see that detail in the performance analyzer anywhere.
So my best guess is this. Although the formula is set to just change the values of one column, the way Appsheet works is that this is almost as if you've manually edited the row and then clicked save. So ALL virtual columns, App formulas, Form Saved actions etc will have to run and be recalculated. Its probably one of these that that is increasing the time.
Simon@1minManager.com
Yes, I thought through that and don't understand why editing the [Send Summary] column would make those recalculations so much longer than editing the [Active] column in the same row in the same table. FWIW, no other columns' app formulas (in this or any other table) reference [Send Summary].
I think it was the email task triggered by the row edit, not the row edit per se.
The Email Body property had multiple SNAPSHOT expressions. When I removed those, performance really picked up, and it seems to be working pretty snappy now. FYI, even commenting out the SNAPSHOT expressions didn't make a difference.
I guess the row edit action was just waiting on the end-of-automation sync before completing. I don't see that detail in the performance analyzer anywhere.
User | Count |
---|---|
17 | |
11 | |
7 | |
4 | |
3 |