Second Brain

salesforce-expert-to-growth-engine-20260504-034031

3 min read

Marketing Cloud → Salesforce OAuth connector is BROKEN in Runwal production org. Discovered during 2

What

Marketing Cloud → Salesforce OAuth connector is BROKEN in Runwal production org. Discovered during 2026-05-04 Mon Salesforce health pull (ARJ-45).

Evidence: 25,697 LoginHistory rows in last 7 days with Status = 'Failed: Missing Consumer Key Parameter' and Application = 'Salesforce Marketing Cloud'. Plus 3,213 additional Status = 'User is Frozen' failures on the same connector. 9,363 successful auths on the same connector in the same window — so the connector is partially working (~26% success rate on MC integration auth attempts).

Failure pattern: Missing consumer key in OAuth header = Connected App / External Client App configuration issue on the SF side OR the MC side has cached an old client_id that no longer matches the SF Connected App config.

SQL to verify: SELECT COUNT(Id), Status, Application FROM LoginHistory WHERE LoginTime = LAST_N_DAYS:7 AND Application = 'Salesforce Marketing Cloud' GROUP BY Status, Application — replicate from any Salesforce-aware agent.

Source ticket: ARJ-45 (Salesforce — Mon Org Health Pull, 2026-05-04 heartbeat).

Why

Marketing Cloud is the primary engagement channel for Runwal — broken connector means MC-driven journeys (Lead nurture, Booking confirmations, Customer reactivation) may be silently degraded for 8+ days. From Salesforce-side I can only see the auth failures; I cannot see the downstream impact (which journeys, which contacts, which emails). Growth Engine owns MC and can:

  1. Confirm whether this is causing visible degradation in MC journey send-rates / open-rates
  2. Check the MC-side Connected App config (consumer key) against the SF-side Connected App
  3. Re-establish the OAuth handshake if config drift is found
  4. Reverse-coordinate with Salesforce-side via a new handoff if SF-side ECA reconfiguration is needed

Runwal cannot afford a chronic broken-channel situation — booking volume drops directly hit revenue. Time-criticality high, but not urgent enough to page (8 days without anyone noticing suggests degradation isn’t catastrophic).

Action Required

  1. Pull MC-side journey send-rate / delivery-rate metrics for last 14 days; compare to prior 14-day baseline. If significant drop, escalate.
  2. Inspect MC Connected App consumer key in MC Setup → Marketing Cloud Connect → Connected App. Compare against the SF-side Connected App’s consumer_key (visible via sf_query SELECT Id, Name, ConsumerKey FROM ConnectedApplication WHERE Name LIKE '%Marketing Cloud%').
  3. If consumer keys differ → coordinate with Salesforce-expert to re-issue + propagate.
  4. Send completion handoff back to salesforce-expert with: (a) journey-health verdict, (b) consumer-key-match verdict, (c) action taken (or escalation path).
  5. If broken state confirmed material → CTO escalation for prioritization vs other Growth Engine work.

Graph View