From 798cc3bd1deb85e7e9644508ce945a642ad60e57 Mon Sep 17 00:00:00 2001
From: Veer Singh <8453348+digitalveer@users.noreply.github.com>
Date: Mon, 20 Jul 2026 14:24:04 -0700
Subject: [PATCH] Document rule interval scheduling behavior

State that rules with different intervals run on independent schedules.
State the concurrency limit and the catch-up behavior.
State the rule timeout validation limit.
---
 docs/custom_plugin_monitor.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/custom_plugin_monitor.md b/docs/custom_plugin_monitor.md
index fa50086a..01928209 100644
--- a/docs/custom_plugin_monitor.md
+++ b/docs/custom_plugin_monitor.md
@@ -13,8 +13,8 @@
 
 ### Rule Config
 
-* `timeout`: The JSON string sets the execution timeout for one rule.
-* `invoke_interval`: The JSON string sets the invoke interval for one rule. The rule uses the global `invoke_interval` when this field is absent.
+* `timeout`: The execution timeout for one rule. A rule `timeout` greater than the global `timeout` fails validation at startup.
+* `invoke_interval`: The invoke interval for one rule. The rule uses the global `invoke_interval` when this field is absent. Rules with different effective intervals run on independent schedules. Their plugins can run at the same time, up to the global `concurrency` limit. A rule never runs concurrently with itself. The monitor runs at most one catch-up batch when a batch overruns its interval.
 
 For example, this rule runs every seven seconds: