arcodash
Start free trial
PlatformConnectorsPricingSecurityDocs
Sign inStart free trial

Troubleshooting

A data source’s connection test fails

The test opens the connection and runs a trivial query — a failure here means arcodash genuinely couldn’t reach or authenticate against your database, not a transient glitch to retry blindly. Check, in order:

  • Is the database reachable from the internet? arcodash Cloud doesn’t publish a fixed set of outbound IP addresses, so if your database’s firewall only allows specific IPs in, there’s no single address to add — you’ll need a broader allowlist or another way to open it up.
  • Is SSL/TLS enabled on the database? Postgres connections default to prefer, which uses TLS when the server offers it and silently falls back to plaintext when it doesn’t. Set the connection’s SSL mode to require (or stricter) if you need the connection to fail rather than downgrade.
  • Are the credentials and database name exactly right? The error message never echoes the secrets you entered, so a typo in a password won’t be visible in the error text itself — retype it rather than assuming it’s saved correctly.

See Data sources overview for what a connection test actually does.

A dashboard opens, but one widget won’t load

This is almost always a permissions gap, not a bug: you can have access to view a dashboard without your groups having access to the data source one of its widgets queries. The dashboard itself opens fine; that one widget just can’t run its query for you specifically. See The permissions model for exactly how dashboard sharing and data-source access are checked independently, and what to ask an admin for to fix it.

You’re getting 429 responses

You’ve hit a rate limit — see Conventions for the exact per-endpoint numbers. There’s no Retry-After header to read; back off for a few seconds and retry. If this is happening on ordinary interactive use (not a script), it usually means something is polling or retrying faster than intended — check for a loop in whatever’s making the requests before assuming the limit itself is the problem.

Both default to expiring 90 days after creation unless a different expiry was set explicitly. Past that, the link resolves as not-found — indistinguishable from one that was revoked. There’s no way to extend an expired link; create a new one from the object’s Share dialog. See Public links and Embedding.

An invitation email never arrived

  • Check spam.
  • Confirm the invite went to the exact address you expect. Accepting requires signing in or creating an account with that exact email — a close-but-different address (a typo, a personal vs. work alias) won’t work even if the person does have an arcodash-eligible account elsewhere.
  • Ask an admin to re-invite the same email. Inviting an address that’s still pending resends the email with a fresh link rather than erroring, so there’s no need to remove and re-add the person first.

See Inviting your team for what the invitee sees once the link does arrive.