Troubleshooting

Concrete fixes for the things that go wrong most often. If none of these match, the FAQ is next, then your APIXX support channel.

A connector is degraded

1. Open the connector from Connectors.
2. Check the recent errors panel — 401/403 means auth; 429 means rate-limit; 5xx means source outage.
3. For OAuth, click Reconnect and re-approve the consent screen.
4. For API key, paste a freshly-generated key.
5. Verify status flips back to active. Flows resume automatically on the next tick.

A run failed with no records processed

• Open the run. The error trace at the top tells you which stage failed: read, transform, or write.
• Read failures are almost always connector health — go check the source connector first.
• Transform failures are mapping issues — open the Mapping Console and look for the failing rule.
• Write failures with 4xx mean the destination rejected the payload — common for missing required fields.
• Click Retry after the underlying cause is fixed.

Lots of partial runs

Partials almost always mean one or two records can't be mapped. Open a recent partial, sort errors by frequency, and you'll usually see the same field path repeatedly. Fix the mapping rule or add a default; partials drop to zero within one tick.

Missing canonical records

1. Confirm the source row actually exists and passes any flow filters.
2. Check the most recent run for that flow — was the record in the cursor window?
3. Open Coverage — the source × entity cell should be green.
4. If everything looks healthy but records are still missing, force a small backfill flow scoped to that ID range.

Schema drift on a source

When a source adds, removes, or renames a field, mapping rules that referenced the old shape start failing. The Mapping Console highlights drift on every flow that touches the affected source. Promote a new mapping version that handles both shapes, then retire the old one.

Hitting a rate limit or quota

Source-side throttling shows up as 429 errors in run logs. Mitigations, in order:

• Lower the schedule cadence on the noisy flow.
• Add a tighter updated_since filter to read fewer records per tick.
• Stagger flows that hit the same source — don't run five Shopify flows on the same 15-min boundary.
• If you're hitting an APIXX plan limit, see Usage & quotas.

Dashboard looks stale

Most pages cache for 30–60 seconds. Click the refresh icon in the top bar to force a re-read. If data is older than a few minutes after a refresh, the cache layer is fine — the upstream flow is the bottleneck. Check its last successful run timestamp.

Can't sign in

• Confirm you're using the work email used at onboarding (SSO sometimes uses a different alias).
• Use the reset-password link. If no email arrives in 5 minutes, check spam and confirm your IT allows mail from noreply@apixx.ai.
• For SSO tenants, hit the IdP login first — Flow won't accept passwords if SSO is enforced.
• Still stuck? Email support@apixx.io from your work address.