Support
Solutions to the most common issues you might encounter with LeakGuard.
"Backend unavailable" banner
ErrorLikely cause
Neon/Cloudflare backend sync is temporarily down or unreachable.
How to fix
Wait a few minutes — LeakGuard automatically falls back to serving data directly from the Stripe API. Most functionality is preserved in fallback mode. If the banner persists beyond 30 minutes, click "Refresh" in the Cache Status bar or contact support.
Metrics show 0 or stale data
WarningLikely cause
Data has not yet been synced for the selected date range.
How to fix
Click "Refresh" in the Cache Status bar to trigger a manual resync. On a new install, the initial sync may take several minutes for large accounts. If your date range was recently changed, allow 5–10 minutes for the new range to populate.
Low attribution coverage (e.g. 40%)
WarningLikely cause
Stripe charges are missing your configured segment metadata key.
How to fix
Go to Settings → Attribution Health. The FocusView shows which charge creation contexts are unattributed. Add the metadata key to those charge creation calls in your application. New charges with the key will contribute to coverage after the next sync.
Evidence table shows only 100 items
WarningLikely cause
Your account is on the Starter plan, which has a 100-item evidence limit.
How to fix
Upgrade to Pro or Business to see unlimited evidence items. Alternatively, narrow the date range — Starter can show all items within a shorter window if the result set is under 100.
Dashboard takes more than 5 seconds to load
InfoLikely cause
Large-volume account with a cold cache after a fresh install.
How to fix
The first load after install may be slower while the backend pre-computes your aggregates. Subsequent loads are typically sub-second. If slowness persists after 24 hours, contact support.
LeakGuard uses read-only Stripe API access. It cannot modify your account, issue refunds, create charges, or access cardholder data. If you see a permission error:
Permission denied on install
Ensure you have admin or developer-level access on your Stripe account. Restricted-key users may not be able to install Stripe Apps.
Missing data for certain objects
Some Stripe object types require specific permissions. LeakGuard requests the minimum required at install. If you revoked permissions after install, reinstall the app to restore them.
Cannot access Reports in the Stripe Dashboard
LeakGuard's Report Runs access is used to fetch historical data for date ranges over 90 days. This is a backend operation — it doesn't affect your Dashboard access level.
You may see gaps or missing days in your trend charts. Common causes:
Days with zero transactions
Days where you had no charges, refunds, or disputes show as gaps or zero values. This is expected — LeakGuard only stores data for days with activity.
Sync delays for historical data
For date ranges beyond 90 days, LeakGuard uses Stripe Report Runs to fetch history. These are async operations that may take 10–30 minutes for large accounts.
Multi-currency rounding
Aggregates across currencies are normalized using the exchange rate at the time of the balance transaction. Rounding can cause sub-cent discrepancies in daily totals.
Refunds crossing billing periods
A refund issued in March for a February charge appears in March's data. LeakGuard attributes events to the date they occurred, not the original transaction date.
If your issue isn't covered here, reach out — we respond to every message.
Contact support →Include your Stripe account ID (you can find it in your Stripe Dashboard settings) and a description of the issue.