The problem isn't merely the batch schedule; the implementation is using an unsupported consent-write path . Salesforce's August 2026 Marketing Cloud Next guidance explicitly warns against using Data 360 batch transforms, streaming transformations, direct data-stream mappings, or bulk APIs to write directly into the Communication Subscription Consent DMO. Those methods can produce consent values that appear stored but aren't consistently honored by the messaging consent layer at send time.

The supported solution is to route the change through Create Consent/Consent Request . A Data 360-triggered flow can listen for the relevant change and invoke Create Consent, which updates the contact point's consent for the required channel and communication subscription through the supported consent service.

Therefore, changing a daily batch to hourly doesn't fix the architectural defect. Switching from batch to streaming transformation also doesn't make a direct DMO write supported.

The master bank correctly identifies B. Salesforce explicitly recommends reissuing incorrectly written consent through a Data 360-triggered flow calling Create Consent.

Study Guide Reference: Consent → Supported Consent Write Methods → Create Consent Action and Data 360-Triggered Flows.