Cloning rows is slower than expected

Hi everyone,

I’m looking for some advice or shared experiences around performance when duplicating data in Glide.

In my app, users can “Save As” a forecast scenario. Behind the scenes, this creates around 10 new rows across 3 different tables, all tied together with a new Scenario ID. For each new row, I’m using a loop + Add Row + Set Column Values pattern to copy over existing values from the current scenario.

What surprises me is that this process is taking around 20 seconds, even though:

  • Each new row only has ~15 columns being set

  • The loop runs over a filtered subset (about 10 rows per table)

  • The tables themselves are not huge

Functionally everything works fine, but the user experience feels slow for what seems like a fairly small amount of data.

My questions:

  • Is this kind of runtime expected for this pattern?

  • Has anyone found a faster, no-code or low-code approach to cloning rows across tables?

  • Are there any best practices to reduce latency when using loops + Add Row + Set Columns?

I’m keen to avoid custom code or external automations if possible, but very happy to learn if there’s a smarter Glide-native way of doing this.

Thanks in advance — any insights would be much appreciated!

I’ve always found the API to be much faster that workflow loops for any sort of bulk add/update actions.

3 Likes