Docs

Manual automation run

A manual run finds matching transactions and applies the field changes stored in the rule. Before applying, Tetri shows the transaction list, match count, and proposed changes.

DocumentationDocsGuideAutomationsAutomation RunDry RunTransaction Changes

Transactions included in the run

A manual run can be limited to a date range. Wallets and transaction types are controlled by the rule conditions. The selected dates appear in the preview and the run log.

Matched transaction examples

Open several matches and compare their current fields with the proposed values. Even if the number of matches looks right, the list may include unrelated transactions.

Changes and run log

Starting the run creates a log entry. Its status and completed actions show whether all matching transactions were processed or some actions failed.

Transactions changed by the run

The run log lists every changed transaction. If the rule changed the wrong records, fix the rule first and then correct those transactions.