Sync history

Every source that syncs has its own sync history: how it is doing right now, and a log of each sync from the last 90 days. Look here when a number seems out of date or a webhook seems not to work.

Where to find it

• In Settings › Sources, open a source's "…" menu and choose Sync history.
• In the sync status at the bottom of the page, choose Sync history under the source.

Only sources that sync have one, so sample data does not.

Health

This card shows how the source is doing right now.

• Status is Up to date, Syncing, Behind schedule or Failed. Behind schedule means the last sync is over two hours old, or a failed sync is waiting for its next try. Failed means the source holds an error, shown under these fields. A sync that was only Partly read counts too. The error stays until a later sync reads everything.
• Last sync is when RevGlance last finished reading the source. A sync stopped by an error does not move it.
• Newest data is the date of the latest payment or subscription change RevGlance has from this source.
• Webhook says whether the provider's calls are arriving. See Webhook status.

When the trial has ended, the card says so, and new syncs wait until you buy RevGlance.

Why Newest data can be older than Last sync

Last sync says when RevGlance read the source. Newest data says how recent the data it found is. A sync can work fine and still find nothing newer:

• App Store: Apple's reports land about a day late.
• Google Play: Google posts its reports within 3 to 7 days.
• Any provider: nothing happened. A quiet stretch with no payments or subscription changes leaves the date where it is.

What starts a sync

Each line in the Sync log says what started it:

Only one sync of a source waits in the queue at a time. A webhook call that arrives while one is waiting joins it, so you can see fewer Webhook lines than calls.

How to read the log

The newest sync comes first. Each line shows when it started, what started it and, for a single sync, how long it took.

Counts

Each kind of record a sync changed gets its own counts: Payments, Subscription changes, Customers, Trials and Cancellations. A count of zero is left out.

• 3 new: records this sync added.
• 2 updated: records RevGlance already had, changed by this sync.
• 4 removed: records that are gone after this sync.

No changes means the sync found nothing to do. Quiet syncs in a row that were started the same way fold into one line, which says how many it covers and how far back they go. That way an hourly sync does not bury the ones that matter.

When a sync has trouble

• Running: the sync is still going. The page updates by itself.
• Partly read: it finished, but part of the provider could not be read. The line shows the error. What it did read is saved and counted, and the next sync reads the same stretch again.
• Failed: an error stopped it. The line shows the error, and anything it read before stopping is saved and counted. Stopped before finishing. means the sync was cut off with no error to show.

RevGlance tries a failed sync again by itself, and each try gets its own line. A Failed line with a clean line above it means the problem went away, so there is nothing to do. If Status still says Failed, the error says what went wrong.

Figures corrected

This lists figures on record that the sync corrected, with the old and the new value. A correction is not something a customer did.

• After a Full re-read: any total that moved, such as MRR, refunds or fees.
• A subscription's MRR: the amount on record for one subscription was corrected.
• A cancellation date: the provider's date for a cancellation differs from the one on record.

A line lists five at most, then and 3 more.

Webhook status

Owners and admins see the webhook's state in Health. It reads one of four ways:

• Last call received, with the time: calls are arriving. There is nothing to do.
• Set up, but no call has arrived yet. The source is ready, but the provider has not called yet. Check that the webhook is added in the provider. Calls come only when something changes, so a quiet source can stay here for a while.
• Not set up, so new data waits for the next scheduled sync. No secret is saved. New data arrives with the hourly or daily sync until you add the webhook.
• Calls are being turned away, with the time of the last one: the provider reaches RevGlance, but its calls fail the check, so they start no sync.

In every state but the first, the card links to the step-by-step guide for your provider.

When calls are turned away

The warning shows after 3 rejected calls in a row, so one stray call does not set it off. Webhook rejected then also shows on the source's row in Settings › Sources. What to check depends on how the provider verifies its calls:

• Stripe, Polar, Lemon Squeezy, Paddle, Recurly: copy the signing secret from the provider again and paste it under Signing secret in the source's Webhook panel.
• Gumroad, App Store, Google Play, Chargebee: make sure the ?token= in the URL at the provider matches the secret saved under Signing secret, or save a new one and update the URL.
• Braintree, Shopify: there is no secret to paste. Check that the webhook was added in the same Braintree account or Shopify app the source connects with.

Calls to a source with no secret saved are rejected too. Saving the secret fixes that.

The warning clears on the next good call or when you save a new secret. If the secret is still wrong, it comes back after 3 more rejected calls. It also goes away 7 days after the last rejected call.

How long it is kept

Each sync stays in the log for 90 days, then it is deleted. Removing a source removes its sync history too.

Who sees what

Everyone in the business can open a source's sync history and read Health and the Sync log. Viewers do not see the webhook's state: no Webhook field, badge or menu item. Starting a sync and saving a secret are for owners and admins. See Team and roles.