Monitor, retry or repair synchronization

In short

Integration details distinguish normal processing from required action. A previously connected account shows Disconnected from [source], no longer updated, never Manual. Record state and latest success, wait for active processing, retry once after a transient error or reconnect the source, then verify one sample account.

Expected result

The connection returns to a usable state and one sample record confirms data is flowing again.

Before you start

Choose a known source account for repair verification.
Keep an authorized invoicing-tool user available for possible reconnection.

Procedure

Open the connection and record state, latest success, and full error.
If processing is active, let it finish without repeated clicks.
After a transient error, start at most one new synchronization.
When Billabex requests reconnection, renew authorization with the source.
Check the new success time, sample account update, and removal of its disconnected badge.

What Billabex does

Billabex preserves attempts and separates authorization state from import outcomes. When a source is removed, it keeps the previous source identity so reconnection remains available and the account is not confused with a truly manual record. Repairing filters can trigger a full import to recover previously excluded accounts.

If the result is not what you expected

Repeated retries do not speed the queue and make diagnosis harder.
If an error returns after reconnection, copy its exact text and time for support.
An active connection with old data calls for latest-run inspection, not automatic reauthorization.