Redash UI does not reflect updated query results from API for queries created by other users

[Morgan-cj]

Issue Summary
When updating query results via the Redash API, the results are successfully refreshed for queries created by the current user (e.g., a new query_result_id is generated, and updated data is returned). However, for queries created by other users, the Redash UI does not display updated results. Instead, the UI continues to show outdated data, even though the API confirms the query has been refreshed. Notably, manually executing the same query in the UI updates the results correctly.

This issue occurs only for queries created by other users, while queries created by the current user are updated correctly in both the API and UI.

Steps to Reproduce

1. Identify a query created by another user in Redash (ensure you have admin rights or sufficient permissions to edit and execute the query).
2. Use the API to refresh the query: Execute POST /api/queries/{query_id}/results with {"max_age": 0}.
3. Verify via the API: A new query_result_id is generated; The returned data from the API reflects the updated results.
4. Open the query in the Redash UI. Observe that:

• The UI displays old results.
• The "Refreshed {}" indicator shows the last time the query was manually executed in the UI.

Why this is a bug:
The API confirms that the query results have been updated (new query_result_id and retrieved_at values are returned).
However, the Redash UI does not reflect these updates, causing inconsistency between the API and the UI.

Expected behavior:
The Redash UI should display the latest results and update the "Refreshed just now" indicator based on the API-triggered refresh, regardless of the original query creator.

Technical details:
Redash Version: 10.1.0 (2589bef)
Browser/OS: Chrome (version 130.0.6723.117)/ macOS 14.1 (23B74)
How did you install Redash: Self-hosted on AWS EC2 instance (details about installation method unavailable)