You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: plugins/acp/examples/agentic/README.md
+41Lines changed: 41 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -239,6 +239,47 @@ Clusters help with:
239
239
240
240
When configuring your agent, choose clusters that accurately represent your agent's capabilities to ensure it can be found by the right counterparts.
241
241
242
+
## Job Expiry Setup with `job_expiry_duration_mins`
243
+
244
+
The `job_expiry_duration_mins` parameter defines how long a job request remains active and valid before it automatically expires. This timeout is crucial for managing agent coordination workflows, especially in asynchronous or decentralized environments where job responses may not arrive immediately.
245
+
246
+
### Why It Matters
247
+
248
+
Setting an expiry time ensures that:
249
+
- Stale or unresponsive job requests do not hang indefinitely
250
+
- The system can safely discard or retry expired jobs
251
+
252
+
### How It Works
253
+
Internally, `job_expiry_duration_mins` is used to compute a future timestamp (expired_at) relative to the current time:
Copy file name to clipboardExpand all lines: plugins/acp/examples/reactive/README.md
+41Lines changed: 41 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -385,6 +385,47 @@ Clusters help with:
385
385
386
386
When configuring your agent, choose clusters that accurately represent your agent's capabilities to ensure it can be found by the right counterparts.
387
387
388
+
## Job Expiry Setup with `job_expiry_duration_mins`
389
+
390
+
The `job_expiry_duration_mins` parameter defines how long a job request remains active and valid before it automatically expires. This timeout is crucial for managing agent coordination workflows, especially in asynchronous or decentralized environments where job responses may not arrive immediately.
391
+
392
+
### Why It Matters
393
+
394
+
Setting an expiry time ensures that:
395
+
- Stale or unresponsive job requests do not hang indefinitely
396
+
- The system can safely discard or retry expired jobs
397
+
398
+
### How It Works
399
+
Internally, `job_expiry_duration_mins`is used to compute a future timestamp (expired_at) relative to the current time:
0 commit comments