Glide tables not Duplicating when Duplicating App (copy sheets)

My app has over 100 Glide tables.

When I duplicate (copy the sheet) historically about 30% of the Glide tables did not populate/copy. I was able to ‘force’ a synchronization by adding an empty row to the table which would ‘kickoff’ the synch and the table would re-populate.

Today - that did not occur, adding an empty row did not re-populate the Glide table.

Glide had duplicated this bug but since their was a work-around it was not a priority.

Have others had issues duplicating their app and not having Glide tables synch? (I also have about 25 google sheets and they all populated correctly).

Thanks

1 Like

It has never occurred to me to double-check app duplicates to verify that they duplicate correctly. When you duplicate an app with “Copy the sheet”, the duplicated app does not point to the correct tables? Or the tables appear in the data editor but all the data is not there?

Tables appears - but none of the data is there.

It is a lot of tables - many just for choice sources - but critical tables too.

51/104 tables were empty.

@Darren_Murphy @DarrenHumphries

This seems to be a timing issue now with Glide back end. I have been retrying every 15 minutes or so. About 90 minutes after my first ‘duplicate’ failure I re-tried the “add row method” and the data began to re-sync properly. Somehow Glide ‘found’ the data after 60 minutes or so.

Recap: Duplicate (copy sheet) fails to synch 50% of my Glide tables. The “add row” workaround failed. After 60 minutes the “add row” workaround succeeded.

Final note: took 21 minutes to re-populate 54 Glide tables. Longest synch was 32 seconds for 142 rows. Shortest sync was 7 seconds 28 rows. Weirdest sync 9 seconds for 2 rows.

I didn’t know about the “and an empty row” thing. I ran into this with a duplicate I was working on that didn’t seem to populate with data from the original.

I see this a lot. I generally don’t get concerned about it because - as you’ve observed - the data eventually shows up.

2 Likes

Yes, it takes times sometimes. Definitely a cache time refresh on server (combined with rate limiting on Linux Nginx server threads).

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.