Salesforce Omni-Channel Auto Status

Stop missing cases and start automating your Salesforce availability. Salesforce Omni-Channel Auto Status Changer — Extension Description What this extension does Automatically changes your Salesforce Omni-Channel presence status based on a daily schedule you define. Instead of manually clicking the Omni-Channel widget every time your shift changes, the extension watches the clock and does it for you. Features Custom status list — define your own statuses that match exactly what appears in your Salesforce Omni-Channel dropdown. Five defaults are pre-loaded (Available - Case, Available - Messaging, Lunch, Screen Sharing, Break) but you can add or remove any. Daily schedule — set multiple time-based rules per day (e.g. 9:00 AM → Available - Case, 1:00 PM → Lunch, 6:00 PM → Offline). Timezone aware — works correctly for any timezone (IST, EST, PST, etc.), auto-detected on first install. Manual override — instantly set any status from the popup without waiting for the schedule. Change log — history of every automatic and manual status change, with (auto) / (manual) labels. Catch-up on wake — if your machine was asleep or screen was locked, on unlock the extension looks back up to 90 minutes and applies any missed status change immediately. Fixes in the latest update Fix 1 — Scheduler was firing immediately on Start Previously, as soon as you turned the scheduler on, it would immediately apply whatever status was most recently scheduled in the past — completely ignoring the configured time. For example, if you had a 9:00 AM "Available" entry and you turned the scheduler on at 3:00 PM, it would instantly change your status to Available. The root cause was that startScheduler() called checkAndApplySchedule() immediately on toggle, and the schedule-matching logic found "the most recent past entry" rather than checking whether the current time actually matched a schedule. This is now fixed — the scheduler only applies a status at the exact configured time, never on startup. Fix 2 — Missed schedules after screen lock or sleep Previously if your screen was locked or machine was asleep when a scheduled time passed, that status change was silently missed and never applied. The extension now checks on every alarm tick: "what status should currently be active, and have I applied it yet?" If a scheduled entry was missed within the last 90 minutes (covering a lunch break, a meeting, or a brief sleep), it is applied immediately on the next alarm tick after unlock. Fix 3 — Alarm frequency increased to every 30 seconds The previous alarm fired every 60 seconds. This is now reduced to every 30 seconds, which halves the worst-case window between a scheduled time passing and the extension detecting it. Fix 4 — Smarter dedup to prevent double-firing The dedup key is now "YYYY-MM-DD|HH:MM|status" — meaning the same scheduled entry cannot fire twice on the same day, but will correctly fire again the next day. Previously the dedup logic could block legitimate fires or allow accidental double-fires. Fix 5 — Clear Log was not working The Clear Log button was correctly clearing data in Chrome storage, but the in-memory state was not being reset before re-rendering. So the log would visually reappear immediately after being cleared. This is now fixed — both memory and storage are cleared together. Known limitation — Why you may see a delay of 10–20 seconds This is a fundamental Chrome browser limitation, not a bug in the extension. Chrome extensions run inside the browser's background service worker system. Chrome intentionally throttles background service workers — especially on machines running on battery, with many tabs open, or with Chrome minimized. This throttling means: The alarm that checks the schedule every 30 seconds may fire 10–20 seconds late on a throttled machine After the alarm fires, Chrome needs 2–5 seconds to wake up the service worker The service worker then sends a message to the Salesforce tab, which takes another 0.5–1 second to click the Omni-Channel dropdown and select the status Best case (office machine, tab focused, plugged in): 3–5 seconds after scheduled time Typical case (background tab, plugged in): 10–15 seconds after scheduled time Worst case (personal machine, battery saver, many tabs): 20–35 seconds after scheduled time This delay cannot be eliminated from within a Chrome extension because Chrome's alarm and service worker throttling is controlled by the operating system and Chrome itself — the extension has no way to override it. If you need precise, zero-delay status changes that also work during screen lock, the only reliable solution is a native desktop application (Python tray app or Windows Task Scheduler script) that calls the Salesforce API directly at the OS level, bypassing Chrome entirely. Screen lock limitation When your screen is locked, the OS suspends Chrome completely. No JavaScript runs, no alarms fire, and the extension cannot make any changes — even if a scheduled time passes while locked. On unlock, the catch-up logic (Fix 2 above) will apply any missed status from the last 90 minutes, but there will always be a delay equal to however long the screen was locked.