Before automatic filing touches a whole stack, you can have it calculated through without changing anything. The dry run shows, for every document, where it would be filed, which tasks it would create and which rule matched. It is the safe way to check a new set of rules – and the fastest way to find out why a document is left behind.
1. Start the dry run
Open Automatic filing and click Automatic processing in the left-hand menu. The button appears as soon as the project has at least one rule for automatic processing.
The window has two buttons at the bottom: Simulate and Start. Simulate changes nothing – the heading then says so plainly: “Simulation — nothing is changed”. Start runs the very same processing for real. Above them you can see how many documents are in the queue.
2. The two checkboxes before the run
Both apply to the dry run exactly as they do to the real one, so the dry run shows you what they do:
- Move duplicates to the trash automatically. One copy is filed, further identical documents go to the trash of the global files. In the dry run such documents are listed as “Duplicate → would go to the trash”.
- File even when only the default rule matches. Off by default. With it on, the case title alone is enough of a match – no keyword rule – and the document lands in the case’s root folder. With similarly named cases that is risky, which is exactly where a dry run pays off. The result line adds “default rule only”.
3. The result builds as it goes
You don’t have to wait for the end: the list fills while the run calculates. At the top “Checked: x / y” counts up, and next to it the groups appear as clickable numbers – Would be filed, Skipped and, if you let duplicates be sorted out, Trash. Click one and only that group is shown; “← Show all” takes you back. In a real run the same groups read Processed instead of “Would be filed”.
For each document you see, depending on what applies:
- Will be filed under – the full target path, with placeholders resolved.
- New name – if the rule renames the file.
- Tasks – how many tasks would be created, or “No task”.
- Rule – the name of the rule that matched, with a pencil beside it: Edit rule opens it right there, without leaving the dry run.
- Matched and Target path – which keywords were found and where they lead.
4. Why a document is left behind
Every skipped document carries its reason. The common ones:
- No matching rule – no keyword hit.
- Tie — no rule is stronger. Several rules match and point at different targets. Below, under Equally strong, you get their names plus what the tie comes down to: the same number of keywords, or several rules set to Always Win. The document stays put, and you decide it yourself in the queue.
- Rule matches, but automation is off. The rule is right, it just isn’t allowed to move anything by itself. Beside it you see what would have happened: “With automation on it would be filed under …” – so you can switch automation on knowing the destination in advance.
- Rule without a target (neither case nor folder) and Placeholders in the target path cannot be resolved – two faults in the rule itself that, without a dry run, would only surface on the real run.
- Rule without keywords, No OCR text, PDF not readable, Duplicate found.
The opposite case also exists: several rules match and the document is filed anyway. When they all want the same thing, asking would be pointless. A filed document then carries “N rules, same target — not a tie” together with their names. That is not a fault; it explains why the tie you would expect from two matches isn’t there.
Good to know
- A dry run writes nothing: no file is moved, no task created, no duplicate sent to the trash.
- You can click a document’s name to open it in automatic filing in a new tab.
- What a real run actually did is in the log afterwards, under Logs.
