Use these limits when choosing how to build and run an automation.
Branches Run One at a Time
Fan-out paths are independent of each other, but ThinkForge runs them one after another rather than at the same time.
Paths Meet Only at a Merge Card
A Tool card or Output card accepts one incoming line. To bring paths together, connect them to a Merge card. The Merge card waits until every line into it has run or been skipped.
Rules Are Exact Comparisons
A condition checks one value in the previous Tool's structured result. It can't read a sentence, combine several checks, or ask an AI model to decide. Have the Tool before a branch return a clear value, such as a category, that a rule can test.
No Loops
An automation can't loop back to an earlier card. The only repetition is For each item on a single Tool card, up to 100 items.
Canvas Runs Start Empty
Run on the canvas always starts with empty input, and document cards are never used as input. The canvas has no way to choose input.
No Retry, Stop, or Resume
When a step fails, the automation stops. It doesn't retry, take a separate failure path, or let you resume from that point. The Automations tab has no Stop button.
Tools Are Always the Current Version
Automations use your current Tools. Editing a Tool changes future runs, and deleting one makes its step fail. You can't pin an automation to an older version of a Tool.
Publishing and Placements
- Publishing replaces the library copy, with no history or undo.
- You can't compare versions or unpublish.
- A placement can't be switched off without removing it.
- Saved file and folder inputs are paths on this computer.
- Optional guidance must use supported local text files. AI-backed Tools read them; missing or unreadable references can stop a run.
Where Automations Can't Run
ThinkForge MCP can't start automations.
A Safe Way to Build
- Make sure a Tool returns a clear structured value before you branch on it.
- For fan-out, set every outgoing line to Always (fan-out).
- For a choice between paths, give every line a condition except one Default route, and give each conditional line a different priority.
- Bring paths together with a Merge card, and give each incoming line a name that says what it carries.
- Keep Maximum items as low as makes sense for the list.
- Test from the place you'll actually run the automation, and check the files it produces instead of relying only on the success message.