For Cortex Cloud customers, a "Redis command timed out" error in the context of GitHub integration typically indicates a temporary issue with the connection between Cortex and its managed Redis instance. These timeouts can cause disruptions in features that rely on Redis, such as GitHub token caching or rate limiting.
These timeouts have been linked to:
Transient connectivity issues between Cortex services and Redis
Occasional problems with the Lettuce Redis client, which may require a pod restart to resolve
Periods of increased latency or brief outages in the Redis backend, sometimes leading to 500 errors or degraded performance for integrations like GitHub
These issues are often transient and may resolve on their own. There is no indication that you need to take any direct action since the infrastructure is managed by Cortex. However, if you notice persistent errors or degraded performance, please contact Cortex support so they can investigate..