Glide Multi-Instance (Primary vs Secondary) Issues

Report a Bug
1

Description

  • Since Glide introduced multi-instance editing (allowing two separate Glide apps to build on the same base), I’ve observed some performance and functionality differences between the primary and secondary instances.

    Here are the main issues:

    1. :high_voltage: Data Sync Delay
      Updating data in the secondary instance sometimes takes 30–60 seconds (or longer) before syncing to the primary instance.

    2. :abacus: Slow Calculations
      Computed columns and logic (especially in large tables) often take much longer — or never finish running — when triggered from the secondary instance.

    3. :laptop: Limited JavaScript Execution
      JS columns either take a long time to compute or fail to compute at all in the secondary instance.

    4. :receipt: Restricted HTML Rendering
      HTML inside Rich Text (RT) components does not render properly in the secondary instance, although it displays correctly in the primary app and in standard text components.

    These inconsistencies suggest that the secondary instance environment is sandboxed or throttled, possibly for stability reasons — but it creates workflow and testing limitations for builders.

2

Can you reliably capture these problems? You should submit a support ticket through the bottom right icon in your builder.

Thank you so much!