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: docs/features/exclusive-mode.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,6 +181,41 @@ timeout = 1800 # Wait up to 30 minutes
181
181
182
182
---
183
183
184
+
## Early Session Release
185
+
186
+
When a workflow spans multiple TM1 instances, RushTI automatically releases sessions from instances that have no remaining tasks — without waiting for the entire workflow to finish. This is especially valuable in exclusive mode, where holding an idle session blocks other RushTI instances from accessing that server.
187
+
188
+
### Example
189
+
190
+
Consider a workflow with 100 tasks: 5 tasks on `tm1-finance` (10 seconds) and 95 tasks on `tm1-reporting` (30 minutes).
191
+
192
+
| Behavior |`tm1-finance` Locked For |
193
+
|----------|------------------------|
194
+
|**Without** early release | 30 min 10 sec (entire workflow) |
195
+
|**With** early release | 10 sec (only while its tasks run) |
196
+
197
+
Once the 5 tasks on `tm1-finance` complete, RushTI logs out from that instance immediately, freeing it for other workflows. The session on `tm1-reporting` continues until its tasks finish.
198
+
199
+
### What You See in Logs
200
+
201
+
```
202
+
Executing task 5/100: RunExtract on tm1-finance
203
+
Early session release: logged out from tm1-finance (no remaining tasks)
204
+
Executing task 6/100: TransformData on tm1-reporting
205
+
...
206
+
```
207
+
208
+
### How It Works
209
+
210
+
- After each task completes, RushTI checks if any pending or running tasks remain for each connected TM1 instance.
211
+
- If an instance has zero remaining tasks, the session is closed immediately.
212
+
- In exclusive mode (`--exclusive`), even preserved connections (via `connection_file`) are released early.
213
+
- In normal mode, preserved connections are kept open for reuse across runs.
214
+
215
+
This feature is always active — no configuration needed.
0 commit comments