Requested by: @suiyangqiu via YakShaver.ai 🦬
cc: @suiyangqiu, @AttackOnMorty, @jimmidier
Hi Team!
🟥 Watch the video (52 sec)
Pain
When a user asks SophieBot for the next SSW event, the bot can return an event that has already occurred. This appears to be caused by SophieBot using UTC time (as per Microsoft Teams default) rather than the user’s local time zone, resulting in past events being considered upcoming.
Acceptance Criteria
- SophieBot determines the current date and time based on the event's local time zone or an explicitly defined time zone.
- Events that have already occurred in the event's local time zone are not returned as upcoming events.
- When asked for the next SSW event, SophieBot consistently returns a future event relative to the user’s local date and time.
- Time zone handling is documented or clearly defined within the SophieBot event logic.
Reproduce Steps
- Open Microsoft Teams (defaulting to UTC time).
- Interact with SophieBot.
- Ask: "What is the next event SSW is running?"
- Observe that SophieBot returns an event dated in the past relative to the user’s local time zone.
Screenshot

Figure: Event query shows a past event because of timezone handling
Requested by: @suiyangqiu via YakShaver.ai 🦬
cc: @suiyangqiu, @AttackOnMorty, @jimmidier
Hi Team!
🟥 Watch the video (52 sec)
Pain
When a user asks SophieBot for the next SSW event, the bot can return an event that has already occurred. This appears to be caused by SophieBot using UTC time (as per Microsoft Teams default) rather than the user’s local time zone, resulting in past events being considered upcoming.
Acceptance Criteria
Reproduce Steps
Screenshot
Figure: Event query shows a past event because of timezone handling