When modifying records, either in bulk or individually, there’s a chance they will not take due to 50x errors, 40x errors, etc. general backend reliability issues.
sometimes you see a little yellow box at the bottom saying errror creating activity, sometimes you can only see this in the network diagnostics tab.
Given copper does not have a service worker, it cannot asynchronously retry this, so this change you’ve made is permanently not going to apply. and, given that its usually not possible to see this, it ends up just being wrong.
What are others doing around this? are you attempting user education to ask them to reload after each change and check? what about in e.g. changing a large number of people in a list, do you export to csv, then make the change, then export to csv again and then diff?
Or have you come up with another way?