fix: address the first review round

- The Access picker offered Slack options that member provisioning would then
  reject: it filtered on `status` but not `configurationStatus`. Rendering the
  field for Slack is what exposed this, so it belongs with that change. Now
  mirrors provisioning, which skips anything not `ready`.
- "The bundled Redis runs without persistence" was only true of the chart. The
  Compose stack leaves Redis on its default snapshotting with no mounted
  volume, so webhook markers survive a restart there but not recreating the
  container.
- Redis is not optional at one replica: CLI authentication's approval store has
  no fallback and throws without it. The values guidance implied the
  requirement began above one replica.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015BwsJTEQRzWJaY4BRCkPZt

Author: waleedlatif1

apps/docs/content/docs/platform/self-hosting/redis.mdx

@@ -26,7 +26,7 @@ Sim uses Redis as a message bus and shared cache. Both deployments ship it by de
 
 Everything Sim keeps in Redis is cache, coordination state, or an in-flight event — never committed data, which lives in PostgreSQL and object storage. Losing or restarting the instance costs active runs their streaming, and a cancellation issued across the gap may not land.
 
-It also costs webhook deduplication. Webhook idempotency markers live wherever the cache does, with a 7-day TTL sized to the longest provider retry window, so a redelivery arriving after a restart can re-run a workflow that already completed — with its real side effects. Billing, checkout, and Chat-send idempotency are pinned to PostgreSQL and are never at risk. The bundled Redis runs without persistence, which is fine for coordination state; if duplicate webhook side effects would be unacceptable for your deployment, point `REDIS_URL` at a managed instance with persistence enabled.
+It also costs webhook deduplication. Webhook idempotency markers live wherever the cache does, with a 7-day TTL sized to the longest provider retry window, so a redelivery arriving after a restart can re-run a workflow that already completed — with its real side effects. Billing, checkout, and Chat-send idempotency are pinned to PostgreSQL and are never at risk. The chart's bundled Redis runs with persistence off entirely, so any restart drops the markers. The Compose stack leaves Redis on its default snapshotting with no mounted volume, so they survive a restart but not recreating the container. If duplicate webhook side effects would be unacceptable for your deployment, point `REDIS_URL` at a managed instance with persistence enabled.
 
 ## Configuration
 

apps/sim/app/workspace/[workspaceId]/knowledge/[id]/hooks/use-connector-member-group-options.ts

@@ -99,7 +99,8 @@ export function useConnectorMemberGroupOptions({
     for (const group of settings.credentialGroups) {
       if (group.status !== 'active') continue
       for (const option of group.options) {
-        if (option.status !== 'active') continue
+        /** Mirrors member provisioning, which skips anything not `ready`. */
+        if (option.status !== 'active' || option.configurationStatus !== 'ready') continue
         if (!isCredentialGroupProvider(option.provider)) continue
         if (getCredentialGroupProviderId(option.provider) !== providerId) continue
         entries.push({

helm/sim/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: sim
 description: A Helm chart for Sim - the open-source AI workspace where teams build, deploy, and manage AI agents
 type: application
-version: 1.9.1
+version: 1.9.2
 appVersion: "v0.8.18"
 kubeVersion: ">=1.25.0-0"
 home: https://sim.ai

helm/sim/values.yaml

@@ -585,7 +585,9 @@ realtime:
 # Redis — pub/sub, the Socket.IO adapter, and the idempotency/progress stores.
 # Bundled by default so a chart install matches the Docker Compose stack.
 # REQUIRED once app.replicaCount or realtime.replicaCount exceeds 1: without it
-# cross-pod events are silently dropped. For production prefer a managed
+# cross-pod events are silently dropped. CLI authentication requires it at any
+# replica count — its approval store has no fallback and throws without Redis.
+# For production prefer a managed
 # instance (ElastiCache, Memorystore, Azure Cache) — set enabled: false and put
 # its connection string in app.env.REDIS_URL, which then takes over.
 redis: