Opened 12 years ago
Last modified 12 years ago
#49 RESOLVED fault
Appetite and Sleep channels transposed in build 2.3 — Gateshead cohort flagged 'hungry at 3am'
| Reported by: | People & Places | Owned by: | M. Ross (Infrastructure) |
|---|---|---|---|
| Priority: | P2 | Milestone: | |
| Component: | SOMA / Somatic Channels | Version: | |
| Keywords: | Cc: | ||
| Desk: | Estate & Systems | Legacy ref: | WBAN-2041 |
Description
Build 2.3 shipped with two column indices swapped in the channel-schedule table, so the Appetite channel fired on the Sleep channel's overnight window. The Gateshead cohort telemetry duly shows the appetite nudge going out at ~03:00 instead of the wind-down prompt — hence a run of readings tagged 'hungry at 3am' in the overnight log. No harm beyond an odd nightly figure and some very confused Tuesday-morning wellbeing scores. Roll the index map back to the 2.2 order and re-issue.
Attachments (0)
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Could the schedule be resolving the wrong channel host after the push? i.e. DNS?
comment:3 by , 12 years ago
It's a column swap in a table, Pike, not a lookup. Confirmed against the Gateshead overnight log — 03:00 appetite prompts, clear as day.
comment:4 by , 12 years ago
Reverted the index map to the 2.2 order, re-pushed, watched a clean night. Wind-down back on the overnight window, appetite back on daytime. Closing.
Two channel indices are transposed in the 2.3 schedule table. Appetite is sitting where Sleep should be, so the whole cohort gets nudged toward a midnight snack instead of a wind-down. Nothing dangerous, just wrong.