Alshival.AiDocs
Open portal ↗

Safe changes and troubleshooting

Resolve access failures and avoid duplicate changes.

Before a write

Confirm the target project, requested change and current tool schema. Write access must be allowed by both your grant and current project permissions. Preserve required confirmation fields, mutation IDs and revisions. Keep upload continuation identifiers for the same upload.

An interrupted change

A timeout or cancellation does not prove a write failed. Inspect current state before trying again. Preserve the original mutation ID and use the source tool’s recovery contract; never submit the same uncertain change as a new mutation. The gateway does not automatically replay it.

Connection problems

SymptomNext step
401 / sign-in requiredCheck expiry or revocation; sign in again or replace the credential through the portal.
403 / project unavailableCheck membership, project permissions, selected workspaces and operations. Reauthentication cannot grant missing access.
Missing projectsComplete pagination, inspect partial failures and check local adapter restrictions.
Consent failsUse the exact HTTPS endpoint and a client supporting remote MCP OAuth. Check the client’s connection diagnostics.
Conflict / stale revisionRead the latest object and reconsider the change before submitting with the correct revision.
Rate limit / service failureReduce concurrency and follow any retry guidance. Determine write outcome before retrying mutations.

Share useful diagnostics

Report the client/version, time, tool name and sanitized status or error. Remove keys, authorization headers, tokens and private project contents from screenshots and logs.