Skip to main content
RudderStack

Delivery failures to salesforce destinations

Degraded Lasted 23h 24m · started · RudderStack's page

Level
confirmed
Worst impact
Degraded
Components
Data Processing Pipeline (US), Data Processing Pipeline (EU)
Regions
eu, us
Down Index
31of 100

What to do

  • Check whether you use RudderStack Data Processing Pipeline (US), Data Processing Pipeline (EU) in eu, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 23h 24m it lasted.

    Anything that failed between 2025-08-14 20:08 UTC and 2025-08-15 19:32 UTC may need a replay.
  • Subscribe to RudderStack's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=rudderstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RudderStack 3

  1. investigating

    We are currently investigating the issue around failures for salesforce destinations

    provider

  2. identified

    The issue has been identified and remediation is being implemented

    provider

  3. resolved

    The incident has been resolved. Recently, Salesforce decided to enforce client_id validation and rolled out changes that made this field mandatory. Fix has been made pass the client_id. Failures have been replayed for all customers with salesforce destinations. Pipelines with rETL sources to salesforce will be processed in the next scheduled sync

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-1cc6bccd42

Is RudderStack still down?

No, this incident was resolved 2025-08-15 19:32 UTC. For RudderStack's live state, see https://down.guide/rudderstack.

How long did it last?

23h 24m, from 2025-08-14 20:08 UTC to 2025-08-15 19:32 UTC, by the times RudderStack posted.

What was affected?

RudderStack named Data Processing Pipeline (US), Data Processing Pipeline (EU) in eu, us.

What caused it?

RudderStack hasn't published a root cause. If it does, it shows here.

Where does this come from?

RudderStack's official status page, https://status.rudderstack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.