Docs: Fallback Mode

.ruby-version

@@ -1 +1 @@
-3.4.2
+3.4.4

Gemfile.lock

@@ -3,18 +3,18 @@ GEM
   specs:
     addressable (2.8.7)
       public_suffix (>= 2.0.2, < 7.0)
-    base64 (0.2.0)
-    bigdecimal (3.1.9)
+    base64 (0.3.0)
+    bigdecimal (3.2.2)
     colorator (1.1.0)
     concurrent-ruby (1.3.5)
-    csv (3.3.2)
+    csv (3.3.5)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
-    ffi (1.17.1)
+    ffi (1.17.2)
     forwardable-extended (2.6.0)
-    google-protobuf (4.29.3)
+    google-protobuf (4.31.1)
       bigdecimal
       rake (>= 13)
     http_parser.rb (0.8.0)
@@ -45,7 +45,7 @@ GEM
       jekyll (>= 3.7, < 5.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    json (2.9.1)
+    json (2.12.2)
     kramdown (2.5.1)
       rexml (>= 3.3.9)
     kramdown-parser-gfm (1.1.0)
@@ -57,16 +57,16 @@ GEM
     mercenary (0.4.0)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (6.0.1)
-    rake (13.2.1)
+    public_suffix (6.0.2)
+    rake (13.3.0)
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rexml (3.4.0)
-    rouge (4.5.1)
+    rexml (3.4.1)
+    rouge (4.5.2)
     safe_yaml (1.0.5)
-    sass-embedded (1.83.4)
-      google-protobuf (~> 4.29)
+    sass-embedded (1.89.2)
+      google-protobuf (~> 4.31)
       rake (>= 13)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)

docusaurus/docs/overview/index.mdx

@@ -92,6 +92,12 @@ However, as explained in the [Queue Mode](#queue-mode-dynamic-split) section, th
 
 In case of network issues, Knapsack Pro logs a warning and automatically switches to Fallback Mode to run your tests with a split based on test file names.
 
+Knapsack Pro will retry to connect with the API multiple times before switching to Fallback Mode.
+
+In the unlikely scenario where some CI nodes switch to Fallback Mode, but others don't, you can expect the following behavior:
+- Queue Mode (default): some tests might be run on multiple CI nodes (you have the guarantee of at-least-once tests execution).
+- Regular Mode: some tests might be skipped; if this is not acceptable, you can [disable Fallback Mode](../ruby/reference.md#knapsack_pro_fallback_mode_enabled).
+
 ## Split by test examples
 
 Knapsack Pro can [parallelize tests across CI nodes by example](../ruby/split-by-test-examples.mdx). This is useful when you have slow test files but don't want to manually split test examples into smaller test files.