Ye switch 2026-07-25 ke mass-SMS haadse ke baad bana tha, aur isi liye ye per-cron toggle nahi hai — wo band karna bhool jaane par kaam nahi aata. MESSAGING_RESUME environment me 1 na ho to har sender andar hi ruk jaata hai: smsService, rcsService, whatsappService, messagingService, aur marketing portal ka seedha Graph sender bhi. Yaani cron chal bhi jaye, patient tak message nahi jaata. Iske alawa har patient-facing cron ka apna per-tenant toggle hota hai aur wo DEFAULT OFF hota hai — naya cron jo patient ko message kar sakta hai, wo bina clinic ke explicitly on kiye kabhi nahi chalta. Aur har patient-facing message unified facade (messagingService) se hi jaana chahiye, seedha whatsappService/rcsService se nahi. Ek aur baat jo bachati hai: jis patient par smsDnd laga hai ya jo deceased mark hai, wo automation ke candidate list se hi bahar ho jaata hai.
Sab messaging emergency me band kaise karu?
Ek hi master switch hai — MESSAGING_RESUME. Wo 1 na ho to WhatsApp, RCS, SMS aur unified facade — sabhi wire par hi ruk jaate hain, cron chalta rahe tab bhi kuch nahi jaata.
Where in ORALZY: Server env (MESSAGING_RESUME) — master; per-tenant cron toggles Settings me
Quick steps
- Turant sab band: MESSAGING_RESUME hata do / 1 ke alawa kar do
- Sirf ek automation band karni ho to uska per-tenant toggle off karo
- Ek patient par: uska smsDnd on kar do