I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. A resident's old 'please call me back' request from Oct 12 was woken up again when she texted about something unrelated (cockroaches), so it paged #alerts as 'waiting 17 days'. Should a new message from someone only restart the chase on an old open question when it is about that same question?
The full question, as raised

rearmChaseOnCustomerMessage (matter-state.ts) clears nagCount/nagBudgetExhaustedAt/escalatedUpAt on ANY inbound from the person, so an unrelated new topic (which opened its own matter) re-runs escalationMatterWorkflow on a stale matter and re-posts stuck-matter-surface. Also the surface copy says 'asked 0 times' because nagCount is reset and nag emails are retired. Option A: re-arm only when the inbound is attributed to that matter (same topic / reply on its thread); otherwise leave the old matter's moved-up stamp alone. Option B: keep R2 as-is (any message re-arms).

Why, and what was tried
The session raising this recommends: Only re-arm on the same question
The new topic already gets its own question and team note; re-waking the old one just re-pages with a misleading day count.
Tried first, unsuccessfully: Traced matter b6679bf2: workflow exhausted 10-13, then the 10-29 roach text re-armed it (matterReopened signal 10-30 01:20), second run exhausted 10-30 15:00, cron moved it up. No other orphaned matters in prod (0 of 320).

da7d6daf is parked on this.

Pick an option above, then press Done.
PropFlow Docs