Troubleshoot login, records and page errors

Keep context and original IDs. Retrying must not create duplicate checks or payments.

Open the workspace

Instructions reviewed

Current workspace availability, quotes and permissions apply. The review date is not a live provider status. Reading help makes no checks or payments.

Before you start

  • Record URL, language, error, time and task ID. Redact keys, codes, names, IDs and full accounts.

Follow these steps

  1. Locate the stage. 401 usually means credentials/session; 403 access/origin; 422 input format; 429 rate/quota.

    You should see： The message maps to a specific recovery action.

  2. Reopen read/login pages. After live-submit timeout, 502/503 or unknown fees, look up the original task, even after signing in again.

    You should see： Restoring access does not create a new live task or payment.

  3. If unresolved, use the feedback draft or contact open@gridzen.ai with redacted IDs and messages, never passwords, keys or recovery codes.

    You should see： Support can locate the issue without another paid reproduction.

Completion check

Resume the original work or provide actionable evidence; uncertain external actions remain unreconciled.

If you get stuck

  • Login loop: check workspace, MFA, cookies and time; do not disable security checks.

Next steps and related guides

Unclear step? Report its location

Include the guide, step, visible message and expected outcome. Redact screenshots. Do not include codes, keys, identity documents, full accounts or customer records.

open@gridzen.ai