What are transfer logs?

Whenever Synci transfers a transaction, it creates a Transfer Log. Because a single financial account can be linked to multiple destinations (see Linked accounts: Send data to destinations), a separate log is generated for each link. Deliveries to your webhook endpoints are logged the same way.

These logs allow you to verify if a transaction was successfully delivered, why it might have been skipped, or exactly what error occurred if a transfer failed.

Where to find them

• On a linked account: Open it from Linked Accounts and go to its Transfer Logs tab to see every log for that link. You can filter the list by status.

• On a transaction: Open a transaction's details and go to its Transfer Logs tab to see every log for that transaction, across all of its links and webhook endpoints.

There's no separate page that lists all of your transfer logs at once. If you need to filter logs by link or by transaction in bulk, you can do that through the API.

Information captured in a log

Each log entry provides key details about the transfer attempt:

• Link ID: The linked account (source account to destination) used for the transfer. Webhook deliveries have no link.

• Transaction ID: A reference to the original transaction received from your account.

• Destination Transaction ID: The unique ID assigned to the transaction by the destination (for example, the YNAB transaction ID) once it is successfully created.

• Status: The current state of the transfer attempt.

• Message: A human-readable description of what happened, often including specific error messages from the destination.

• Date: When the log was created.

Log statuses & their meaning

Transfer logs move through several statuses during their lifecycle:

Retrying failed transfers

When a transfer fails, Synci tries that transaction again the next time it transfers to the link, usually after the account's next sync. After 5 failed attempts in a row on the same link, Synci stops retrying that transaction automatically.

You can also retry by hand:

• On a link's Transfer Logs tab, select the logs you want and choose Retry all transfers from the Actions menu.

• In a transaction's details, Retry transfer tries again on every link of that transaction's account.

• On the Transactions page, select transactions and choose Retry all transfers.

Each transaction can be retried by hand once per minute per link. Once a transaction has failed 10 times on a link, Synci refuses further manual retries for it on that link.

Retrying a transaction that was already transferred won't duplicate it in Google Sheets or Notion, which skip transactions that already have a Transferred log on the link. If YNAB or Lunch Money reports it as a duplicate, the new log shows Transfer Failed with a "Transaction already exists" message.

Undoing a transfer

If a transaction was sent to the wrong place or you simply want to remove it, you can Undo the transfer. Undo works for YNAB, Lunch Money, Google Sheets and Notion.

• In a transaction's details, use the Undo button next to a log on its Transfer Logs tab.

• On a link's Transfer Logs tab, select logs and choose Undo all transfers from the Actions menu.

• On the Transactions page, select transactions and choose Undo all transfers to undo every transferred and updated log of those transactions.

How it works

When you trigger an Undo:

1. Deletion: Synci deletes the transaction from the destination using the stored Destination Transaction ID. In Google Sheets the row is deleted, and in Notion the page is moved to the trash.

2. Audit Trail: A new log with the status Deleted Transaction records the undo, and the original log is marked as undone.

3. No automatic re-send: Synci won't send an undone transaction to that link again on its own. Google Sheets and Notion skip it even if you retry it. For YNAB and Lunch Money, a manual retry sends it again, unless the destination reports it as a duplicate.

Constraints

• Only logs with a Transferred or Updated status can be undone.

• A transfer cannot be undone if it has already been undone previously.

• The log must contain a valid Destination Transaction ID to know what to delete.

• The link must still exist. Once a link is deleted, the transfers it made can no longer be undone.

Troubleshooting with transfer logs

Transfer logs are your first stop when "missing" transactions occur:

• Check for Skipped: If a transaction isn't showing up at your destination, check whether it was marked Skipped Transfer, either by a rule or because it was already in the sheet or database.

• Read the message: If a log says Transfer Failed, its message contains the error from the destination.

• Check the link: If the destination connection is disabled or stops responding, Synci pauses the link and notifies you. Nothing is transferred until you resume it.

• Bulk Actions: If a large batch of transactions was sent incorrectly, select them and use Undo all transfers to remove them all at once rather than one by one.

Pro tip: Using filters

On a link's Transfer Logs tab, filter by status to find failed or skipped transfers quickly. To see every destination a single transaction was sent to, open that transaction's details instead.

How long logs are kept

Transfer 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.