We resolved a timezone bug in the Social Post Scheduler that caused posts to publish at incorrect times for users outside the UTC+5 timezone. If you are still seeing unexpected publish times after this fix, contact our support team and we will investigate your account directly.
🔍 What Happened
The Social Post Scheduler was reading your scheduled times against the server's UTC+5 offset instead of your local timezone. For example, if you scheduled a post for 2:30 PM Eastern Time (UTC−5), the system treated it as 2:30 PM UTC+5 — causing the post to fire hours away from your intended time.
The size of the time drift depended on how far your local timezone sits from UTC+5:
- Users in timezones near UTC+5 experienced minor discrepancies.
- Users further from UTC+5 — such as Eastern Time (UTC−5) or London (UTC+0) — saw significantly larger offsets.
🛠️ Workaround Steps
Posts that were scheduled during the incident may have published at incorrect times or not at all. We cannot retroactively correct or republish those posts. If you had important content affected, please reschedule it using the corrected system. All posts scheduled after this fix will publish at the correct time — no further action is required.
📡 Engineering Status
Our engineering team has identified and resolved the root cause. Scheduled times are now stored and displayed in UTC, and the Social Post Scheduler correctly converts your local timezone input before saving. This fix applies to all posts scheduled going forward. This fix also resolves the issue where scheduled posts were not visible in the Calendar view. The UI continues to block past dates from being selected; any attempts to schedule a post in the past via other methods will be rejected.
📞 When to Contact Support
Reach out to our support team if any of the following apply:
- You are still seeing posts publish at unexpected times after this fix.
- Pending posts in your queue are showing incorrect scheduled times.
- You need help identifying or rescheduling posts that published at the wrong time during the affected window.
🌀 We sincerely apologize for any disruption this caused to your publishing schedule — if you have further questions or need hands-on help with affected posts, contact our support team and we will investigate your account directly.