2026-09-29 · board row gk-collections-gates · fix #13489 (deployed to the Temporal worker 04:03Z)
When a company switches Collections off, the daily collections walker must not start any chase and no reminder drafts may be written there. The walker's first run after the deploy, at 09:00 UTC, did exactly that.
| Check | Result |
|---|---|
Chase enrolments refused as collections_module_off (09:00–09:08Z) | 71 |
| Collections reminder drafts at Collections-off buildings since deploy | 0 |
| Buildings resolving Collections off (3 companies) | 84 (13 test) |
| Control: drafts in 30 days at Collections-on buildings | 1 (2026-09-26) |
Example line: 2026-09-29 09:01:16Z refusing chase enrolment — collections_module_off (property=bench-company-line-live-1 …)
CloudWatch Logs Insights on /aws/ecs/propflow-renewal-worker-prod, filter refusing chase enrolment — collections_module_off from 08:55Z: 71 matched of 401 scanned. DynamoDB read of CollectionsDunReview rows created since 04:03:46Z, grouped by the building's resolved Collections switch (company setting with building override): none. Read-only; no writes. Resident names and AppFolio subdomains omitted.