Troubleshooting

Connect issues

Channel keeps showing needs_reconnect — the provider revoked Sosyabot's token (user revoked authorization, password change, security event). Re-run the connect flow from Connections.
OAuth callback 404 — the redirect URI registered with the provider doesn't match <BASE_URL>/api/v1/auth/<platform>/callback. See OAuth Callback URLs.
Telegram bot can't post — bot is not a member or admin in the target chat. Add it via the chat settings in Telegram.

Scheduled posts don't fire — verify the worker is running with ./service.sh status. Check ./service.sh logs worker for stack traces.
Post stuck in pending — the BullMQ queue lost the job. Re-trigger with PATCH /api/v1/posts/:id/status { status: 1 }.
Image upload fails with 413 — image exceeds Storage cap (default 50 MB).

Image generation returns 402 — workspace AI credits exhausted. Upgrade or wait for the cycle reset on the 1st.
Inline AI returns generic errors — the configured Qevron model isn't available. Test from AI Models → Test.

OTP email never arrives — verify SMTP from Admin → SMTP and re-send the test email. Check spam.
Stuck on "verify your email" — admins can flip isVerified: true manually from Users.
Rate-limited — auth endpoints cap at 10 / 15 min, OTP at 20 / 15 min. Wait or contact your admin.

Stripe webhook events not landing — your endpoint STRIPE_WEBHOOK_SECRET doesn't match the dashboard secret. See Stripe Webhook setup.
Subscription stuck in past_due — the most recent invoice failed. Re-attempt payment from /app/upgrade or fix the card.