Castwyn
Help CenterCommon errors
Every error message Castwyn shows, what it means, and the fix. Copy the exact text from the app and find it below.
“No OpenAI/Anthropic key saved. Add one on the Keys page.”
Where: Compose, Voice preview, API
Why: Castwyn is bring-your-own-keys: generation runs on your own AI key, and none is saved for that provider.
Fix: Go to AI keys and paste an OpenAI or Anthropic API key. Keys are encrypted at rest and only used for your generations.
“OpenAI error 401 / Anthropic error 401”
Where: Compose, week generation, API
Why: Your saved AI key is invalid, revoked, or expired.
Fix: Create a fresh key in your OpenAI/Anthropic dashboard and re-save it on the AI keys page.
“OpenAI error 429 / Anthropic error 429”
Where: Compose, week generation
Why: Your AI provider is rate-limiting you or your credit balance ran out.
Fix: Check your provider's billing page. Week generation runs in small batches to stay under limits, but an empty balance stops everything.
“Start your free 7-day trial from the dashboard to unlock Castwyn — no credit card needed.”
Where: Any create/generate/publish action
Why: Your trial or subscription isn't active.
Fix: Open the Dashboard and start the trial (no card), or manage billing if your subscription lapsed.
“Account is not connected.”
Where: Publish now, scheduled publishing
Why: The post targets a network you haven't connected (or whose connection was removed).
Fix: Open the network under Networks in the sidebar and connect it, then retry the post.
“Threads connection expired. Reconnect your Threads account.”
Where: Threads publishing
Why: Threads tokens last about 60 days. Castwyn auto-refreshes them near expiry, but a long-idle connection can lapse.
Fix: Open Networks → Threads and reconnect. Takes ten seconds.
“Bluesky connection is incomplete. Reconnect.”
Where: Bluesky publishing
Why: The stored Bluesky app-password session is missing pieces (usually after a password change on Bluesky's side).
Fix: Open Networks → Bluesky and reconnect with a fresh app password.
“This network doesn't support direct publishing yet — use Copy & open to post manually.”
Where: Queue, Publish now
Why: The network posts via copy & paste for now (direct scheduling is coming soon; Substack has no public API), so Castwyn can't publish to it automatically.
Fix: Use the Copy & open button — your post is copied and the network opens for a one-click paste. Then hit Mark as posted.
“Already published.”
Where: Queue
Why: You tried to publish or reschedule a post that already went out.
Fix: Nothing to do — duplicate publishes are blocked on purpose. Generate a fresh post if you want to say it again.
“This post is already being published.”
Where: Queue, API
Why: Two publish attempts raced (double-click, or the scheduler picked it up at the same moment).
Fix: Wait a few seconds and refresh — the first attempt finishes and the post shows as published.
“That time is in the past.”
Where: Scheduling
Why: The schedule time you picked is earlier than now (timezone mix-ups are the usual culprit).
Fix: Pick a future time. The picker uses your device's local timezone.
“Missing or invalid API token. Send it as: Authorization: Bearer cwn_…”
Where: REST API, MCP
Why: The request has no token, a typo'd token, or a revoked one.
Fix: Create a token on the API & MCP page and send it exactly as shown in the examples there. Tokens are shown once — if lost, revoke and create a new one.
“Post not found.”
Where: REST API, MCP
Why: The post id doesn't exist or belongs to a different account.
Fix: List your posts first (GET /api/v1/posts or the castwyn_list_posts tool) and use an id from the response.
Error not listed, or the fix didn’t work? Send it to support with the exact text.