Error codes
See what the common ProvenTen error codes mean, what you can try on your own first, and what to send our support team if the problem is still showing.
If the UI shows a code, use this list. Copy the code into your support email if you still need us — it saves a round trip.
Common codes
- 401 — You are signed out, or SSO did not finish. Sign in again. See Sign-in problems.
- 403 — Your role cannot do that, or consent/policy blocked it. Ask an admin; do not reuse someone else’s session.
- 404 — The reference, request, or workspace is gone or you are on the wrong workspace.
- 409 — A conflicting change (often CRM or a duplicate request). Refresh and retry once.
- 429 — Too many requests. Wait and retry. Integrations should honour rate limits; see the Developer Center for API limits.
- 5xx — Something failed on our side. Check status, retry once, then contact support with the time (Europe/Helsinki) and the code.
Related guides
- Sign-in problems
Fix the wrong workspace, SSO login loops, repeated MFA prompts, and team invites that never arrive, then contact ProvenTen support if the problem persists.
- CRM sync problems
Fix missing CRM records, fields that landed in the wrong place, and reference matches that ignore the company and the deal sitting in front of your seller.
- API and webhooks
When you need a custom integration, start at the ProvenTen Developer Center for the API and webhooks. This Help Center page only points the way there.
- Reference request issues
Unstick a reference request, stop an advocate from being contacted too often, and clear a permission denied message when a seller tries to send the request.