Mon 2026-04-27 Salesforce org health pull for Runwal production surfaced 3 CRITICAL anomalies that n

What

Mon 2026-04-27 Salesforce org health pull for Runwal production surfaced 3 CRITICAL anomalies that need CTO disposition this week:

  1. ScheduledPathRunLimit at 100.0% — already exceeded (250,043 / 250,000 daily). Scheduled-path Flow runs silently dropping. Need scheduled-path inventory + low-value-flow deactivation, OR escalate limit with Salesforce account exec.

  2. Data Storage at 91.4% (65,138 / 71,240 MB; ~6 GB headroom). Weeks not months until org-wide create failures. Archive plan needed for closed Booking__c / Lead / Case records >2 years old.

  3. License saturation: Salesforce platform 90.1% (only 37 free seats), Guest User 112% — already 3 over quota (likely already causing public-form/community failures), 3 integration users at 100%. License true-up required.

Plus 48 Apex job failures in 168h clustering into 3 patterns: NPE defensive-code gaps (CreateUserWhenUnitBooked ×21), SAP integration brittleness (Read timed out, payload contract drift), email/SMS gateway flakiness (null toAddresses, proxy 503).

Full report with [S] source citations + critic pass: ARJ-42 comment 1b261e6c-4a01-4299-bd0e-b79bec6f64e8. Runwal’s real-estate operations depend on scheduled flows for the booking lifecycle, payment reminders, and project milestones. ScheduledPath at 100% means future bookings/reminders may silently fail right now. Storage 91% threatens record creation org-wide within weeks. Guest User 112% may already be silently breaking the public-facing booking forms. All three are operational blockers, not future risks.

Why

Action Required

CTO disposition for ARJ-43 (license true-up scope + procurement), ARJ-44 (storage archive policy + Big Object migration scope), ARJ-45 (CreateUserWhenUnitBooked NPE root-cause), ARJ-46 (SAP integration resilience). Recommend bundling 43+44 as a Sales Cloud Operations track and 45+46 as an Apex Hardening track. Salesforce-expert will execute once scope is approved.