Client does not update on change to coded and custom component

Bug reports
1

Sometimes it takes time, or the client does not update at all, after a coded or custom component is edited.

For example: Edits to coded component is not reflected in client. Refreshing browser does not fix the problem. Moving the component to a different place updates the component’s position on the client, but not the content of the component. The component was updated after we created another object in Create, e.g. a text box.

1 Like
2

Hi @eirik.k,

Thank you for describing the issue.

I just tested editing a coded component and a custom component, and the changes were reflected immediately on my end. To help us understand better, could you check the following:

  • Is Live Preview enabled?
  • Does this happen across all your applications or only in one?
  • Does it happen in all browsers or just a specific one? Could you try different browsers?

If the issue persists, it would be super helpful if you could attach a short screen recording showing the problem in action. That might give us some more insight into what’s going on.

3

Hi @Simona

This also affects other elements than coded components, usually if there is a property as a function.
We also have problems now and then with deleting elements, they get deleted from create, but stick around in the app for everyone, refreshing or changing browser does not work.
The only way to make it actually disappear is to create a sibling element, then it usually disappears immediately.

The state in Create is synced correctly to all clients, but it seems like the state in Create is not synced correctly to the app.

I have only seen this issue when we are 3 or more working, doing a lot of changes at the same time.

4

Hi,

Based on your description, this might be caused by the size of the app, combined with several people working simultaneously in Dev. Since autodeploy is always enabled in Dev, frequent updates in a large app can result in heavy and rapid deployments, which may cause state mismatches like the ones you’re seeing.

To investigate further, it could be useful to:

  • Tidy up the app a bit (check App Health) to reduce its size.
  • Try to set up a new, empty app with multiple users working at the same time. If the issue doesn’t occur there, it would point to app size or structure as a contributing factor.

We don’t have a concrete fix yet, but this might help narrow down the root cause.