Hi team, is rules_UNSTABLE working as intended? we are targetting the filter chips in Liveboard and we noticed this has stopped working. We did upgrade to the latest SDK version recently.

'[data-testid="filter-panel-chip"][data-tooltip-content*="Value:"]': {
    '--ts-var-chip-background': '#D8EFFD',
    '--ts-var-chip-color': '#00588F',
  },

message has been deleted

Yes — what you’re seeing is consistent with expected behavior for

rules_UNSTABLE

.

rules_UNSTABLE

is explicitly documented as unstable and can break across ThoughtSpot upgrades (including SDK/platform UI changes). So a selector that used to work (especially one based on

data-testid

/

data-tooltip-content

) may stop matching after an upgrade. Also, for selector-based overrides, ThoughtSpot docs recommend adding

!important

to rule properties, otherwise base styles may win. ### What to do now 1. Re-inspect the chip element in your upgraded instance (the selector likely changed). 2. Add

!important

to properties in

rules_UNSTABLE

. 3. Prefer CSS variables where possible (more stable than DOM selectors). Your current snippet updated with `!important`:

js
customizations: {
  style: {
    customCSS: {
      rules_UNSTABLE: {
        '[data-testid="filter-panel-chip"][data-tooltip-content*="Value:"]': {
          '--ts-var-chip-background': '#D8EFFD !important',
          '--ts-var-chip-color': '#00588F !important',
        },
      },
    },
  },
}

### More stable alternative (recommended) Use supported chip variables directly (applies broadly to filter chips):

js
customizations: {
  style: {
    customCSS: {
      variables: {
        '--ts-var-chip-background': '#D8EFFD',
        '--ts-var-chip-color': '#00588F',
      },
    },
  },
}

If you want, I can help you build a post-upgrade-safe rule strategy (minimal selectors + fallback variables) for Liveboard chips specifically.