# Not All Changes Reflect When Pushing a Client Update Until Client Restart **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [January 20, 2022, 8:38pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226 "2022-01-20T20:38:59Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Derek\_Ulee](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@Derek\_Ulee](https://forum.inductiveautomation.com/u/Derek_Ulee)\ **Post date:** [January 20, 2022, 8:38pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/1 "2022-01-20T20:38:59Z")
When pressing save in the designer to push a change to an active production environment I have seen that some clients will not reflect the changes properly. For example, after updating with a change to the column attributes of a table on the screen, the newly added columns which should have been hidden were displayed to the user on some clients until the client was restarted. This was accompanied by an error on these select clients, but unfortunately I don’t have record of the error currently. Is there any specific things that could cause a change like this not to reach a client, after the client receives the update? ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [January 20, 2022, 8:45pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/2 "2022-01-20T20:45:50Z")
I don’t think a client restart is needed. Do you see the same behavior when closing and reopen the window (without restarting the client)? ---
**Author:** ![Derek\_Ulee](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@Derek\_Ulee](https://forum.inductiveautomation.com/u/Derek_Ulee)\ **Post date:** [January 20, 2022, 8:58pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/3 "2022-01-20T20:58:14Z")
Yes when this occurred swapping windows did not resolve the problem. It was as though the new version of the window did not get applied to the client until the user logged out from the Command \> Log Out function or closed and restarted the client completely. ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [January 20, 2022, 8:59pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/4 "2022-01-20T20:59:16Z")
For this particular window I would change cache policy to Never. ---
**Author:** ![Derek\_Ulee](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@Derek\_Ulee](https://forum.inductiveautomation.com/u/Derek_Ulee)\ **Post date:** [January 20, 2022, 9:18pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/5 "2022-01-20T21:18:52Z")
This window, as well as nearly all others in the application use a cache policy of “Never.” ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [January 20, 2022, 10:22pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/6 "2022-01-20T22:22:06Z")
🤷‍♂️ Try contacting support. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [January 21, 2022, 12:56pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/7 "2022-01-21T12:56:56Z")
I’ve seen this where the cache gets ‘corrupted’, for lack of a better term. Deleting the cache seemed to do the trick for me. ---
**Author:** ![Noah\_St\_Mark](https://avatars.discourse-cdn.com/v4/letter/n/7ab992/32.png) [@Noah\_St\_Mark](https://forum.inductiveautomation.com/u/Noah_St_Mark)\ **Post date:** [August 28, 2025, 2:47pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/8 "2025-08-28T14:47:38Z")
> [@Derek\_Ulee](#): > > seen that some clients will not reflect the changes properly. For example, after updating with a change to the column attributes of a table on the screen, the newly added columns which should have been hidden were displayed to the user on some clients until the client was Can you explain the cache? What directory does the cache live in? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 28, 2025, 2:48pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/9 "2025-08-28T14:48:42Z")
> [@Noah\_St\_Mark](#): > > What directory does the cache live in? In your client-side home directory under the `.ignition` folder. ---
**Author:** ![Noah\_St\_Mark](https://avatars.discourse-cdn.com/v4/letter/n/7ab992/32.png) [@Noah\_St\_Mark](https://forum.inductiveautomation.com/u/Noah_St_Mark)\ **Post date:** [August 28, 2025, 3:01pm UTC](https://forum.inductiveautomation.com/t/not-all-changes-reflect-when-pushing-a-client-update-until-client-restart/55226/10 "2025-08-28T15:01:03Z")
Thanks Phil!