What's the delay for SPICE? I know data overview does not update often (and can be annoying), but are other SPICE tables the same? 

I saw it today with the translation assessment and translation productivity assessment data sets. I have seen the error message as well with other non-SPICE data sets in the past. The error just makes it difficult as you are trying to build out visualizations.

I disagree with this one. I find that the data in a spice is cached and doesn't update as quickly as the datasets that are not in a spice.

I should also mention that there are pros and cons to migrating datasets to SPICE. While it can improve performance, it introduces a delay before updates are reflected, meaning we lose real-time visibility into the data. For this reason, we review each dataset on a case-by-case basis to determine whether migrating to SPICE is appropriate, rather than applying a one-size-fits-all approach.

Hi Russell,

Can you please share the specific details for this issue in a support ticket, including the name of the analysis where you are seeing the issue and the dataset being used? I'm already in contact with Support on a separate reporting-related topic that was raised by one of your team members, so I will look into this issue at the same time.

Cheers,

Ian