Documentation Index
Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
Use this file to discover all available pages before exploring further.
Connector tests are only the first check. A connector can authenticate successfully while a real payment, tax, label, print, bank-feed, or marketplace workflow still fails because the record data is incomplete or the external service rejected the action.
Start From Integrations
Open Integrations and review connector health, mode, logs, tests, and sync activity before changing records.
Triage Order
- Confirm the entity is using the correct sandbox or production mode.
- Check whether the connector is connected, disconnected, expired, or in error.
- Open connector logs or the Sync Dashboard.
- Test the connector if the card offers a test action.
- Test the actual workflow with a small safe record.
- Fix record data, connector credentials, webhook setup, or external permissions based on the failure.
- Re-run the workflow and confirm the external service and Arcus agree.
Common Failure Types
| Failure | What it means | First recovery step |
|---|---|---|
| Authorization expired | External service no longer accepts the saved credential or token. | Reconnect or rotate credentials from the connector card. |
| Disconnected | Future sync or actions are stopped. | Reconnect only after confirming the correct external account and mode. |
| Webhook failure | External service events are not reaching Arcus or cannot be verified. | Confirm webhook URL, secret, event list, and external subscription status. |
| Sync delay | Import or export is behind. | Open Sync Dashboard and compare inbound versus outbound activity. |
| Sync drift | Arcus and the external service disagree on status, inventory, price, or fulfillment. | Identify the source of truth, then re-sync or correct the record intentionally. |
| Stale external record | The external order, product, listing, or payment no longer exists or changed. | Use connector logs and record actions to clear stale IDs or re-import safely. |
| Mode mismatch | Sandbox connector is used for production work or production connector is used for testing. | Stop, confirm the entity, and reconnect with the correct mode. |
Marketplace Drift
Marketplace drift means Arcus and the marketplace disagree. Common examples include:- Marketplace order changed after import.
- Fulfillment was updated outside Arcus.
- Listing SKU no longer matches the Arcus product.
- Inventory changed externally.
- Price changed on the marketplace but not in Arcus.
- A Shopify order or product was deleted after Arcus cached its external ID.
Payment, Shipping, And Tax Checks
- Stripe: check key mode, webhook secret, payment result, authentication requirement, saved method health, dispute state, and payout timing.
- Shippo: check addresses, package dimensions, weight, carrier service, customs fields, label status, and webhook updates.
- PrintNode: check connector health, local workstation client, selected default printer, queue status, and failed jobs.
- AvaTax: check addresses, tax codes, exemption state, marketplace facilitator rules, document strategy, and resync errors.
- Plaid: check bank authorization, linked account, sync result, and reconciliation match state.
- RingCentral: check credentials, extension mapping, manual sync, webhook subscription, and recording availability.
Related Articles
Connector Dashboard
Review connector mode, health, masked credentials, tests, logs, sync dashboard, and safe reconnect steps.
Marketplace Connectors
Connect Shopify, Amazon, and eBay, review sync settings, mapping, webhooks, logs, and marketplace blocks.
Stripe Payments
Configure Stripe keys, webhooks, payment workflows, saved methods, reconcile, payouts, and disputes.
Shippo and PrintNode
Configure Shippo for rates, labels, tracking, and voids, and PrintNode for labels and document printing.