Apache Superset When the "Force refresh" option is applied after a dashboard filter -the filtered data no longer appears for all dashboard users

Bug description

When the "Force refresh" option is applied after a dashboard filter -the filtered data no longer appears for all dashboard users. 1. Go to https://bi.ol.mit.edu/superset/dashboard/p/Y2rqpXGqG6z/ 2. Filter down to one "learner email" value 3. Apply the "Force refresh" option to the report

See if that learner email is still searchable after refreshing the page
If that learner is now gone the bug still exists

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

Browser

Chrome

Additional context

No response

Checklist

[x] I have searched Superset docs and Slack and didn't find a solution to my problem.
[x] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Comment From: dosubot[bot]

Hey @KatelynGit! I'm here to help you with your bug report and answer any questions you have. Let's work together to resolve this issue!

The issue you're experiencing, where data disappears for all dashboard users after applying a "Force refresh" with a dashboard filter, might be related to specific conditions in the codebase. There is a known issue where charts sometimes show 'No Results' even when data exists, requiring multiple force refreshes to display the data correctly. This problem is linked to the Redis cache configuration, which might be affecting the visibility of data after a force refresh ^[1].

To address this, you might want to review your Redis cache settings and ensure they are correctly configured. Here is an example of a typical Redis cache configuration:

CACHE_CONFIG = {
    'CACHE_TYPE': 'redis',
    'CACHE_DEFAULT_TIMEOUT': 300,
    'CACHE_KEY_PREFIX': 'superset_results',
    'CACHE_REDIS_HOST': env('REDIS_HOST'),
    'CACHE_REDIS_PORT': env('REDIS_PORT'),
    'CACHE_REDIS_PASSWORD': env('REDIS_PASSWORD'),
    'CACHE_REDIS_DB': env('REDIS_DB', 1),
}
DATA_CACHE_CONFIG = CACHE_CONFIG

If the issue persists, it might be beneficial to investigate further into the caching mechanism or consider reaching out to the development team for more insights.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

Comment From: rusackas

Can you provide a video of before/after so we can better assess?

Comment From: rusackas

I'm unable to reproduce this. It's also been silent for quite a while. If you're still facing this, DM me on Superset Slack or ping me here, and we can revisit this.