What are rule logs?

Every time Synci evaluates a rule against a transaction, it creates a log entry for each action it attempts to take. Whether the action was successful or failed (e.g., due to an invalid expression or an API error from YNAB), a log is recorded to help you understand exactly what happened "under the hood."

You can access these logs directly from your Synci dashboard or via the API to see the history of changes applied to any specific transaction. In the app, you'll find them:

• Under Rules > Logs in the sidebar, for all of your rules.

• On a rule's Logs tab.

• On the Rule Logs tab of a bank account or a linked account.

• On the Rule Logs tab of a transaction's details.

Information captured in a log

Each rule log contains detailed metadata about the operation:

• Rule & Action: Identifies exactly which rule and which specific action within that rule was triggered.

• Transaction Reference: Links the log to the specific transaction that was affected.

• Field Changes: Shows the Field that was targeted, the Previous Value before the rule ran, and the New Value applied by the rule.

• Status & Result:

  • Success: A Rule applied badge (or true via API) indicates the rule action was applied successfully.

  • Failure: A Rule failed badge means the action failed. The log captures a Message explaining why, for example an error returned by YNAB or Lunch Money, or a Liquid filter that received the wrong type of value.

  • Undo: A log created by an undo shows a Rule undone badge.

• Timestamp: The exact time the action was executed (Executed At).

The "Undo" feature

Another powerful feature of rule logs is the ability to revert changes. If a rule incorrectly modified a transaction, you can "Undo" that specific action directly from the log: use the Undo button next to a log in a transaction's details, or select logs in any rule log list and choose Undo rule actions.

Supported actions

Currently, you can undo actions that set values:

• Set Field (changes a rule made to your data in Synci)

• Set YNAB Field (data sent to YNAB by older rules)

• Set Lunch Money Field (data sent to Lunch Money by older rules)

Actions built with the current rule builder for rules that apply only on the way out (destination fields and output fields) can't be undone. If you try, you'll see "This action cannot be undone."

How it works

When you trigger an Undo:

1. Synci looks at the Previous Value stored in the log.

2. It restores that value to the transaction (either in Synci or by sending an update to YNAB or Lunch Money).

3. A new log entry is created to track the undo action itself, ensuring the audit trail remains complete.

4. The original log is marked as undone, with an Undone At timestamp.

Limitations

• Depth: An action can be undone/redone up to 3 times in a chain to prevent infinite loops or data corruption.

• Newer changes: If a newer log changed the same field on the same transaction, the undo is refused with "Cannot undo this action as more recent modifications exist." Undo the newer change first.

• Logic-based actions: Actions like Stop transfer cannot be undone because they prevent the transaction from being processed further; there is no "previous value" to restore.

Searching and filtering logs

In the app, you can filter the list to find exactly what you need:

• By status: Show only Rule applied or Rule failed logs, to quickly identify the rules that are failing so you can fix your configurations.

• By rule: On the Rules > Logs page, see all activity for a specific rule you've created. A rule's own Logs tab does the same.

To see every rule that touched a specific transaction, open the transaction's details and go to its Rule Logs tab. Filtering by transaction, by field (like amount or mapped_fields.description) or by linked account is available through the API.

Pro tips for troubleshooting

• Check the Message: If a rule isn't working, the message field in a failed log is your best friend. It usually contains the exact error returned by the destination service (YNAB/Lunch Money).

• Check mapped fields: Rule logs show the previous and new value of fields like mapped_fields.payee and mapped_fields.description. If the starting value isn't what you expected, you can write a rule to clean it further. Or, you can change which fields Synci uses for them in the Map fields section of the account's Settings.

• Sequence Matters: If multiple rules change the same field, check the timestamps. Rules are processed in order, and logs will show you the cumulative effect of these changes as the transaction moves through your pipeline.

How long logs are kept

Rule logs are deleted automatically, along with your transactions, once they are older than your Data retention period. A log's age counts from when Synci created it.