# Why does my X scheduler keep asking me to reconnect? > An X scheduler asks you to reconnect when its short-lived login can't refresh, usually after a password change or a revoked app. Here's how to fix it. - Published: 2026-10-09 - Last updated: 2026-10-09 - Author: Sanju (Founder & CEO @ DunSocial) - Topics: x, tips --- Your X scheduler asks you to reconnect because the login it holds for your account stopped working & could not be renewed. The usual causes are a password change, removing the app from X's connected apps, a suspension, or the scheduler losing access on its side. X is also mid-way through a change to how apps sign in, which is worth knowing even though it rarely needs anything from you. ## Why X connections need renewing When you connect X to a scheduler, you are not handing over your password. You approve an app, & X gives that app a token. X's tokens are short-lived by design. A scheduler that publishes while you are asleep has to ask X for a fresh token again & again, using a longer-lived refresh token it stored when you connected. If that refresh fails, the scheduler has no valid login left & the only option is to send you back through X's approval screen. ## The usual reasons a reconnect is needed - **You changed your X password.** This revokes tokens that were issued under the old one. - **You removed the app from X.** Check X → Settings → Security and account access → Apps and sessions → Connected apps. If the scheduler is missing, access was revoked. - **Your account was suspended or locked.** Tokens stop working until the account is restored, & then you reconnect. - **The scheduler's own access to X changed.** If nothing changed on your side, the cause may be the tool's. **Fix:** reconnect through the scheduler, then publish a test post & confirm it appears on X. Reconnecting does not retroactively publish a post that was due while the account was disconnected, so reschedule it. ## What X changed in September 2026 X's developer changelog added a way for apps to move users from the older OAuth 1.0a sign-in method to OAuth 2.0 without showing the user a new approval screen. It was listed on September 21, 2026. X's documentation describes OAuth 1.0a as being retired. We have not found a published shutdown date, so treat this as a slow migration rather than a deadline. For you, the practical effect is small. A scheduler that already uses OAuth 2.0 with a refresh token is not affected. A scheduler still on the old method has to migrate its stored connections, & if that goes badly you may see a reconnect request you did not expect. ## How DunSocial handles X connections DunSocial connects to X with OAuth 2.0 & refreshes each X connection on a schedule, about every 90 minutes, so a token rarely lapses while a post is waiting. When a connection does fail, you hear about it instead of finding out later: - **Reconnect in a couple of clicks** from your connected accounts. - **Get a webhook the moment it happens.** DunSocial sends `social_account.reconnect_required` & `post.publish_failed`, so a Slack or Discord message can reach you in minutes. - **See it on the calendar.** A failed post stays visible so you can reschedule it once the account is back. Setup for the alerts is covered in [DunSocial webhooks: get notified when a post publishes or fails](/blog/dunsocial-webhooks-get-notified-when-a-post-publishes-or-fails). The wider list of causes is in [why did my scheduled social media post fail](/blog/why-did-my-scheduled-social-post-fail), & if you are unsure scheduling is allowed on X at all, read [is scheduling posts on X against the rules](/blog/is-scheduling-posts-on-x-against-the-rules). ## A quick checklist when X asks you to reconnect 1. Check that your X account can post directly. If it is locked or suspended, fix that first. 2. Look at Connected apps on X to see whether the scheduler is still listed. 3. Reconnect through the scheduler & approve the permissions again. 4. Publish a test post. 5. Reschedule anything that was due while you were disconnected. ## Try it DunSocial is a flat **$20/mo** or **$192/yr**, with a 14-day trial & no card required. [Start the trial](https://app.dunsocial.com/login) & connect X in a couple of clicks. ## FAQ ### Why does X disconnect more often than other platforms? X issues short-lived access tokens, so a scheduler has to renew them constantly through a refresh token. If a single renewal fails, the connection drops. Some platforms issue longer-lived tokens, so they need renewing less often. ### Is X shutting down OAuth 1.0a? X's documentation describes it as being retired, & the September 21, 2026 changelog entry added a migration path to OAuth 2.0. We have not found a published shutdown date, so check X's changelog for updates. ### Do I lose my scheduled posts when I reconnect? Posts stay in your calendar, but a post that was due while the account was disconnected does not publish by itself. Reschedule it after you reconnect. ### Will changing my X password disconnect my scheduler? Yes, it can. A password change revokes tokens issued under the old password, so plan to reconnect afterwards & publish a test post. ### Can I review before go-live? Yes. Drafts wait for your confirmation before anything is published, including drafts written by AI. ## Sources - [X API changelog (September 21, 2026: OAuth 1.0a to OAuth 2.0 token exchange)](https://docs.x.com/changelog) --- ## About this document This is the Markdown representation of https://www.dunsocial.com/blog/why-does-my-x-scheduler-keep-asking-me-to-reconnect. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`. Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt ## Company - Product: DunSocial, https://www.dunsocial.com - Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India - Support: support@dunsocial.com - Open the app: https://app.dunsocial.com/login