For the complete documentation index, see llms.txt. This page is also available as Markdown.

Troubleshooting and support

Start with the current workspace, signed-in account and exact error. Those three facts resolve many apparent missing-data problems.

Problem
What to check

Workspace is missing

The invited email address, accepted invitation and current membership.

Feature or action is missing

Your role, plan and whether the workspace has that capability enabled.

Documents or companies seem absent

Workspace, selected folder/list/board, filters and restricted access.

Upload finished but the Analyst cannot use the file

Processing state and Upload history, not just transfer completion.

Analyst appears stuck

Existing job status, queue, source access and credits before resubmitting.

Output contains the wrong facts

Company identity, source selection, reporting period and cited evidence.

Export fails or looks wrong

Save/generation completion, error details, size and the exported file's actual layout.

Integration does not return information

Connected provider account, authorization, granted permissions and capture scope.

Automation did not run

Enabled state, trigger, timezone, quiet period, target and run history.

Email did not arrive

Recipient and delivery record; generation success alone is not delivery.

API request fails

HTTP status, key scope, expiry, membership and workspace API access.

Excel data or changes are wrong

Linked document, current workbook, selected rows, mapping and history.

Recover without duplicating work

Before retrying a paid or mutating action, inspect its existing result. A browser timeout does not prove that a job failed to start. Repeating a create, send or import can produce duplicate work.

Use a targeted retry when offered. Fix an invalid source, permission or expired connection first. Keep useful partial results while investigating the remaining error.

If a page fails to load, preserve any unsaved text before reloading. Recheck the workspace after signing in again. If the issue is limited to a particular file or row, use a synthetic example to reproduce it when possible.

Report a useful issue

Send your CorpDev.Ai representative:

  • The feature and workspace affected.

  • What you tried, what you expected and what happened.

  • The time and timezone.

  • The exact error and relevant document, job or run identifier.

  • Whether the problem repeats and whether other work still functions.

Include a redacted screenshot if it helps. Do not send passwords, API keys, provider tokens or unrelated customer information. If a confidential file is needed for diagnosis, agree on an appropriate transfer method first.

Suspected access or sharing issue

Stop the affected sharing or integration flow, revoke an exposed key or link where appropriate, and contact your representative with the relevant identifiers and time. Preserve the evidence needed to investigate. Do not test suspected access problems against another organization's workspace.

For normal setup questions, return to Getting started, Workspaces or API access.