dosubot[bot] commented on issue #30670:
URL: https://github.com/apache/superset/issues/30670#issuecomment-2428482236

   <!-- Answer -->
   I found a similar open issue titled [Async queries and Cache not working as 
expected](https://github.com/apache/superset/issues/30650), which was last 
updated on October 21, 2024. This issue might be related to your problem of 
Superset being stuck in a loading state. Here are some steps you can take to 
troubleshoot and potentially resolve the issue:
   
   1. **Redis Configuration**: Ensure that your Redis configuration is 
correctly set up in the `superset_config.py` file. Check that the 
`CACHE_CONFIG` and `DATA_CACHE_CONFIG` are correctly pointing to your Redis 
instance and that the `CACHE_TYPE` is set to `'RedisCache'`.
   
   2. **Async Queries Configuration**: Verify that the `GLOBAL_ASYNC_QUERIES` 
feature flag is enabled and that the `GLOBAL_ASYNC_QUERIES_TRANSPORT` is set to 
`'polling'` or `'ws'` as per your setup.
   
   3. **Celery Configuration**: Make sure that the Celery broker and result 
backend are correctly configured to use Redis, and that the Celery workers are 
running properly.
   
   4. **JWT Secret**: Ensure that the `GLOBAL_ASYNC_QUERIES_JWT_SECRET` is set 
correctly, as this is crucial for async query authentication.
   
   If the issue persists, you might want to look into the specific error 
messages or logs related to async queries and caching in Superset 4.0.2, which 
can provide more detailed insights into what might be going wrong 
<sup>[[1]](https://github.com/apache/superset/issues/30650)</sup>.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to