# Fix app connection problems

Start in **Settings → Apps** and check which connection path you used. **Connect your apps** and **Sign in directly** are separate connection methods; an app you built with Nock is listed under **My Apps**. The right fix depends on the path and the status shown on that app's row.

## The sign-in page opened, but Nock still says it is connecting

Finish signing in to the app in the browser window and approve the access request. Return to Nock and wait for its connection status. If the sign-in expired or failed, start **Connect** or **Sign in** again to get a fresh session. A saved connection is not proof that the external sign-in completed.

## Nock asks me to sign in to Nock

Sign in to the Nock account you want to use, then try the app connection again. If the account service is unreachable or times out, restore your network connection and retry after Nock can reach the service.

## The app is connected, but Nock says agent access is off

Open **Settings → Apps** or the notch's **Apps** tab and turn on that app's **Agent access** switch. This lets Nock use the connection you already made; it does not require signing in again. If the connection itself has expired, reconnect it as well.

## I do not see an interactive app card

Only some directly connected apps supply interactive cards. Check **Settings → Apps → Official → App widgets** and make sure **Allow app widgets** is enabled for that app. If the app does not provide a card, or its card cannot load, Nock can still show a regular answer or [media card](/nock/connected-app-media). App cards are separate from widgets you build for your Mac; see [Interactive app cards](/nock/app-widgets) and [Build a widget](/nock/widget-builder).

## The app asks me to set it up or connect my own account

Follow the app-specific instructions shown in Settings. Some services need a connection the app owner must configure, or a separate sign-in you complete in the browser. Nock cannot complete an external account's consent or setup on your behalf. Do not paste passwords, access codes, or provider keys into an ordinary chat message.

## An action failed, or I am not sure whether it happened

Check the destination app before retrying a message, post, or other change. A timeout does not always mean the external service rejected the action, so retrying immediately could create a duplicate. Nock asks for approval before supported actions that send or delete; review the approval card before allowing the action.

## Still having trouble

Reconnect the affected app from its own connection card, then check its status and the next request. If Nock reports a plan or usage limit, see [Usage and limits](/nock/usage-limits) and [Usage troubleshooting](/nock/usage-troubleshooting). For per-app access controls, see [Control app access](/nock/app-access-controls) and [Disconnect an app](/nock/disconnect-apps).