Fix a problem

Find what you're seeing and the guide that fixes it: a Chirp that doesn't answer, a key or model problem, a blank embed, a domain that won't connect, a paused account and more.

EveryoneFor: Anyone

When you're done, you know which guide fixes what you're seeing.

Who this is for: anyone with a problem: Chirp owners and their team, and students in an Academy. If you're a visitor and a Chirp doesn't work, tell the person who shared it: only they can fix it.

Find what you see below and open its guide. Each one starts with the exact messages, so you can match the words on your screen.

Your Chirp doesn't answer

Sharing and your website

Building

AI apps

Your account

Academy

The quickest check

If one of your Chirps doesn't answer, ask it something in the preview:

  1. Open Chirps in the menu and click Edit on the Chirp (View if you're a viewer).
  2. In the preview on the right, click a conversation starter, or type a message and press Enter.

When the Chirp can't answer, the preview says why in plain words, and what to do. Visitors never see these messages: they get a short, general one.

When the Chirp can't answer, the preview says why.

If the preview answers but visitors still get a message, it's one of the things the preview skips:

  • Pause and daily limits. Pause this Chirp and the daily limits under 10. Visitor limits never stop your own preview.
  • Access checks. An access code, password, invitation list or email step isn't asked of you in the preview.
  • The published version. The preview uses what you last saved. Visitors get the published version, so a fix to something like the model reaches them only after Publish changes.

Visitors see "temporarily unavailable" or a busy message covers each of these. Working in a workspace someone shared with you? The preview gives you the reason too, worded for you.

Paused can mean three things

Checked against the app on October 28, 2026.