Validate an Auto-Sync Rule with Dry-run

What Dry-run does

Dry-run checks an existing rule against current Documents content without processing files or creating jobs. It is the safest way to confirm the scope and file filters before enabling automation or using Run Now.

The dialog shows:

• the total matching document(s) found; and
• sample documents with filename, content type, and size when available.

Run a Dry-run

1. Open Rules.
2. Find the rule card.
3. Click Dry-run.
4. Wait for the result dialog.
5. Compare the matching count and sample with the intended source.
6. Click Close.

Dry-run can be used while the rule is enabled or disabled. It does not consume document-processing work because it only evaluates matches.

Interpret the result

The result is correct

Enable the rule for future matching uploads. If existing matching files should also be processed, click Run Now and monitor Job History.

Too many documents match

Edit the rule and narrow one or more of:

• scope mode;
• Workspace, Application, Page, or Field;
• selected users or roles;
• Flow Builder Workflow or Node Label;
• allowed extensions; or
• PDF page limit.

Run Dry-run again after each material change.

No documents match

A zero result can be valid when the rule targets future uploads. Otherwise, check:

• whether matching files already exist;
• whether the scope points to the correct source;
• whether file extensions exclude the expected type; and
• whether the PDF page limit excludes the file.

Dry-run fails

Close the dialog, refresh Rules, and retry. If it continues to fail, confirm that the Knowledge service and the source content are available.

Dry-run compared with Run Now

Always use Dry-run before a broad Run Now action.