Skip to main content
Most Arcus messages are protective. They usually mean the record needs missing setup, permission, approval, payment, inventory, connector, or accounting-period review before the action is safe.

​
Read The Message In Context

Open the record detail page and review status, banners, tabs, and related records before retrying the action.
Order detail page with customer context, status badges, action buttons, addresses, documents, progress, and line items

Detail pages show the record context that explains why an action is blocked or disabled.

Use this order:
  1. Read the exact message.
  2. Confirm the selected entity and environment.
  3. Confirm your role and location access.
  4. Check the record status.
  5. Check required setup.
  6. Check related workflow state, such as payment, invoice, fulfillment, return, approval, connector, or accounting period.
  7. Fix the cause and retry once.
  8. If it still fails, capture the message and send the record link to an admin or support owner.

​
Common Messages

​
Disabled Buttons

Disabled buttons are often clearer than errors. Hover or read nearby banners when available, then check:
  • Status: draft, open, posted, paid, fulfilled, cancelled, archived, or voided.
  • Permissions: role and location access.
  • Required setup: account, product, address, terms, tax, connector, or printer.
  • Approval: order, PO, bill, journal entry, or period close approval.
  • History: payment, invoice, shipment, return, refund, credit, or GL activity.

​
Connector Errors

Connector errors need two checks: connection health and real workflow data.
Integrations dashboard with connector cards, status counters, sandbox and production indicators, and error counters

Integrations shows connector health, mode, logs, tests, and sync activity before you retry external workflows.

Examples:
  • Stripe can be connected, but a card can still require authentication.
  • Shippo can be connected, but an address or package can still fail carrier validation.
  • PrintNode can be connected, but the workstation client or printer can still be offline.
  • Plaid can be connected, but a bank can require login refresh.
  • Shopify can be connected, but webhooks or mapping can still fail.
  • AvaTax can be connected, but tax can fail because address or tax-code setup is incomplete.

​
When To Escalate

Escalate when:
  • A customer could be charged incorrectly.
  • Inventory would move incorrectly.
  • A shipment label would be purchased twice.
  • Accounting would post into the wrong period.
  • A connector appears to affect production unexpectedly.
  • A message mentions data isolation, access, or unauthorized action.
  • The same error repeats after setup has been corrected.

Common Statuses Across Arcus

Understand common order, payment, fulfillment, return, purchasing, accounting, and connector statuses.

Order Exceptions and Recovery Choices

Recover from holds, approvals, backorders, overcharges, marketplace blocks, and failed auto-pack.

Connector Troubleshooting

Recover authorization failures, webhook issues, sync delays, mode mismatch, and stale external records.

Period Close

Understand blocked posting, reopen requests, force close, and accounting-period rules.