Troubleshoot an AI connection

Use these checks without copying credentials or client information into a support request.

The tool scan fails

1. Confirm the endpoint is exactly https://mcp.stenz.app/mcp.
2. Check gateway health and readiness.
3. Confirm your provider or workspace allows custom connectors or developer-mode apps.
4. Remove and recreate the draft connection if it still holds an old tool snapshot.

Authentication repeats or expires

• reconnect from the provider and complete the Stenz consent screen;
• check whether the connection was paused, revoked, or lost a required subscription;
• make sure you are signed in to the intended Stenz artist account before accepting;
• never send a token, cookie, authorization code, or password to support.

A tool is missing

Check the Stenz subscription, OAuth permissions, connection policy, allowed forms, and provider-side disabled tools. A newly added permission may require a new consent flow.

An action remains pending

Open Stenz → AI assistants → Approvals or use the Stenz link returned by the assistant. Check expiry, the current resource version, and whether a recent Stenz session is required.

Do not retry an ambiguous financial or client-visible effect manually. Contact support with the safe diagnostic fields below.

Safe information for support

You may share:

• date, time, and timezone;
• provider and client version;
• tool name;
• safe error code;
• correlation identifier;
• redacted intent or delivery status.

Never share a token, secret, cookie, client e-mail or phone number, request content, message body, media, or provider payload.