Probably should have mentioned how I am doing the caching to make it clear. First time grid is loaded with the default config it captures the things which are dropped by the state directive

captureTemplates(columns) {
  columns.forEach(column => {
    const template = (({ header, formatter, cellClasses, cellStyles, bodyTemplate }) =>
      ({ header, formatter, cellClasses, cellStyles, bodyTemplate }))(column);
    this.templates.push(template);
  });
}

I then subscribe to the onColumnInit and restore column templates using

restoreColumnTemplates(column) {
  const columnTemplates = this.templates.find(c => c.header === column.header);
  if (columnTemplates) {
    Object.assign(column, columnTemplates);
  }
}

The reason for doing it this way is we already had a lot of logic written into the html for custom templates, formatters, styling etc. So when we wanted to use the state service and found it dropped all those while giving state this was a more generic way to ensure those were kept and reapplied to the view.

Yes that is similar to my use case. I figured out the problem is related to the custom toolbar I have around the state service as if I remove that it works fine. What I am doing there is caching the custom styling, functions etc applied to the columns and then reapplying those to the state service output since it drops those. So when user applies a view it will reapply the original functions and handling. Seems like due to that the approach isn't working. Although it definitely did in 9.1.2 as that is currently in production and working fine. I guess the column is already linked to the object rather than the reference and so doing this.highlight = {...this.highlight} isn't impacting those columns. Not too sure how it was working before. Is there a way I can get that to work? Or a different way to ensure the styling is reapplied?