EFSJ CRM v2
The rep-facing CRM rebuilt on the HEARTWOOD spine. Ruled the real intake by Eddie 2026-08-27. Fixtures-first, one seam from efsj-core.
Active queue
Public-safe issue order, with the most urgent work first.
- #1P1Triagedthis week
[Bug] Guides index says the app runs on fixture data that resets on restart, but in...
Queue updates automatically - #2P2Triagedthis month
Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy
Queue updates automatically - #3P2In Progressthis month
May a Heartwood seat (estimator, operations manager) create a rep's follow-up task from a quote request, or does the rep keep being told…
Queue updates automatically - #4P2In Progressthis month
"Nobody else puts tasks on a rep's list": does that mean no other person, or do system follow-ups on sent papers stop landing directly too?
Queue updates automatically
Recent activity
Last 7 public eventsUpdated Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy
Updated Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy
Updated Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy
Moved Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy → [object Object]
Filed Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy
Filed Railway shows efsj-crm-v2 crashing at every deploy swap (Kevin's 2026-10-12 report): Next exits 143 on SIGTERM and docs-only pushes redeploy
Shipped Is "change order" now the one word for what was an acknowledgement, or are they still two papers? And is "On a work order" a paper status…