Using the Sync Console and Retrying Failed Transactions

Who this is for: Property managers, board members, and accounting staff on a PREMIUM property with QuickBooks Online connected, who need to check on or retry a transaction that failed to sync.

What the sync console is

The sync console is where you go to see the health of your QuickBooks Online connection and fix anything that did not make it across. It lives inside property Settings, in the QuickBooks Online drawer. Opening it gives you two tabs:

• Connection: connection status, company details, and a general Sync Now button.
• Sync History: the reconciliation checkpoint link, the Failed Transactions list, the Attention (drift) section, account mapping, and the full raw sync log.

This article covers the Sync History tab, specifically the Failed Transactions list and how to retry from it.

Note: If your property has never connected to QuickBooks before, the drawer shows a setup wizard instead of these two tabs. That first-time connection flow is covered in the "Connecting QuickBooks Online to URBI" guide.

How to open it

1. Go to property Settings.
2. Open the QuickBooks Online drawer.
3. Click the Sync History tab.

Reading the Failed Transactions list

Each row in the Failed Transactions section is one thing URBI tried to send to QuickBooks and could not. From left to right, a row tells you:

• Transaction type, shown in bold (for example Invoice, Bill, Payment, or Journal Entry).
• The operation being attempted, shown underneath the type in smaller text (what URBI was trying to do with that record).
• A status badge, either Failed or Voided. See the Voided section below.
• Attempts, shown as "N attempts" (this only appears once URBI has tried more than once).
• The error message from QuickBooks, shown in red, if one was returned and the row is not voided.
• Enqueued, the date and time the sync attempt was originally queued.

The section header, Failed Transactions, carries a count badge showing how many rows are currently in the list. If the count is 0, you will not see the badge at all, and the list shows an empty state instead: "No failed syncs, every recent push to QuickBooks succeeded, failed items will appear here with their error and a Retry action."

The list loads 25 rows at a time. If there are more, you will see a Load more (N more) button at the bottom; once a page comes back with fewer than 25 rows, that button is replaced with "You have reached the end."

Note: Retrying requires PREMIUM-tier accounting and manager-level access. If you are staff without manager permissions, you will not be able to use Retry, this is enforced automatically and is not a bug.

How to retry a single failed transaction

1. Find the row for the transaction you want to retry.
2. Click Retry on that row.
3. The row disappears from the list right away.

That disappearance happens immediately, before anything has actually happened with QuickBooks. Behind the scenes, Retry does not talk to QuickBooks directly. It resets the item to a "waiting to sync" state and clears its old error, which puts it back in line for URBI's regular background sync process. The actual push to QuickBooks happens a short time later, on that process's next pass, not the instant you click.

How to know it worked: the row does not come back. There is no separate "success" message, a retried item that succeeded simply never reappears in the Failed Transactions list.

How to know it failed again: the row reappears with an error, once you refresh or the section reloads. This is not a live, instant notification, it shows up on the next load of the section. To make sure you never miss a repeat failure, URBI also raises a persistent error notification when a retry attempt could not even be queued (for example, if the request to queue it failed outright). That notification does not auto-dismiss, you have to close it yourself. This is deliberate: an auto-dismissing notification could disappear before you noticed a real failure.

How to retry all failed transactions

If you have several failed items and want to requeue all of them at once:

1. Open the Sync History tab and scroll to Failed Transactions.
2. Click Retry all in the section header.
3. The button disables and shows a spinner with the label "Retrying all..." while the request is in progress.
4. When it finishes, a toast appears confirming how many were requeued, for example "3 syncs requeued."
5. The list refreshes automatically.

Like the single-row Retry, Retry all is not instant against QuickBooks either, it queues every failed item for another attempt, and the actual pushes happen in the background afterward. Retry all automatically skips rows tied to a URBI record that has since been voided (the same rule described below for a single row), so it is safe to use even when your failed list has a mix of old, voided, and current items.

When Retry is grayed out

Both Retry (on a row) and Retry all (in the header) are disabled whenever your QuickBooks connection is broken. You will see a small hint next to the affected controls: "Reconnect QuickBooks before retrying," along with a shield icon on the disabled Retry all button.

Retrying against a broken connection cannot succeed, since there is nothing on the other end to receive the push, so URBI blocks the action until the connection is fixed rather than let you queue attempts that are guaranteed to fail again. See the "Reconnecting a Broken QuickBooks Connection" guide for how to fix the connection itself.

Understanding the Voided state

Sometimes a row shows a Voided badge instead of Failed, and instead of a Retry button, there is nothing to click.

What it means: the URBI record this failed sync was trying to send (the invoice, expense, or journal entry) has since been voided inside URBI. Since the source record no longer stands, there is nothing left worth pushing to QuickBooks, so URBI does not offer a Retry action for it.

The one exception: if the failed item's own job WAS to push the void itself over to QuickBooks (in other words, the attempt that failed was the "tell QuickBooks this got voided" step), that row still shows Retry, not Voided. That attempt is still worth retrying, because QuickBooks needs to hear about the void even though the underlying record is gone.

Note: You cannot tell from the badge alone whether a row is the "send the void" attempt or an ordinary voided-and-abandoned row, just look for whether a Retry button is present. If it's there, it's still actionable.

The "Map account" shortcut

In the Failed Transactions header, next to Retry all, you may see a Map account button. Clicking it jumps you down to the account mapping section of the same tab.

What it is: a general shortcut to account mapping, useful when you suspect an unmapped account is behind one or more failures.

What it is not: a guarantee that the specific row you clicked from is caused by a mapping problem. URBI cannot yet tell, row by row, whether a given failure is a mapping issue or something else. If the red error message on a row does not mention mapping or accounts, account mapping is probably not what is wrong with that row, and clicking Map account will not fix it. Read the error message on the row first before assuming mapping is the cause.

Sync Now vs Retry (do not confuse these)

The Connection tab has its own button, Sync Now, separate from anything in Failed Transactions. It is a general, on-demand trigger that kicks off a sync pass across the connection, it is not the same thing as retrying one specific failed item. While it runs, the button shows a spinning icon and the label "Syncing...". Use Sync Now when you want to nudge a general sync along; use Retry (or Retry all) when you are dealing with specific items that already failed and are sitting in the Failed Transactions list.

FAQ

Does clicking Retry guarantee success? No. Retry only queues another attempt, it does not guarantee QuickBooks will accept it this time. If the underlying problem (a mapping issue, a validation error, a QuickBooks-side rejection) has not been fixed, the item can fail again.

How do I know when a retry actually completes? You will not get an instant confirmation. If the retry succeeds, the row simply never comes back to the Failed Transactions list. If it fails again, the row reappears with its error the next time the section loads, so check back or refresh after a few minutes.

Can I retry the same item over and over? Yes, there is no limit on retry attempts, and the row's "N attempts" count will keep climbing. But retrying repeatedly without addressing the underlying error (shown in red on the row) usually just produces the same failure. Read the error first.

What if I have a lot of failed transactions, should I use Retry all or go one by one? Use Retry all first, especially if the failures look like they share a common cause (for example, a connection that was recently reconnected). It requeues everything at once and safely skips voided rows. Go row by row only when you want to fix and retry specific items individually, for instance after correcting one account's mapping and wanting to confirm that fix worked before requeuing everything else.

What if a failed item never seems to leave the list? That means every retry is failing again. Read the red error message on that row, it is the most reliable clue to what is actually wrong (a mapping problem, a QuickBooks-side validation issue, and so on). If the connection is broken, reconnect first, since no retry can succeed against a broken connection. If the error message is unclear or the item keeps failing after you have addressed what it describes, that is worth flagging to support.

Related articles

• Handling Drift: Re-Push to Restore
• Reconnecting a Broken QuickBooks Connection
• Understanding QBO Sync States and Errors