We have introduced a workaround that is expected to prevent Salesforce workflow connections from failing 30 days after credential creation or refresh. Based on our testing, this issue should no longer impact Qualtrics to Salesforce connections going forward. We are continuing to monitor the situation before confirming full resolution.
ACTION: Connections that were already affected prior to this fix will not recover automatically. If you are impacted and have not yet done so, please navigate to the impacted workflow and either refresh the Salesforce credential or create a new credential and save, to restore the connection.
NOTE: If the Salesforce Outbound Message connection is broken, triggering the workflows will fail with no apparent message on the Qualtrics side and no new runs will be visible in the Run History. There will be a gap between current time and last execution. The failed Outbound Messages can be observed in Salesforce: Setup -> Environments -> Monitoring -> Outbound Messages, see failed outbound messages.
Posted Sep 04, 2026 - 14:53 UTC
Identified
Due to an issue surfacing with enablement of recently introduced Salesforce mandatory security controls, some Qualtrics workflows connecting to Salesforce will start failing exactly 30 days after credentials being created or refreshed, with a message indicating that the credential connection has expired or is invalid.
ACTION: These connections will not recover on their own. Restoring them requires a one-time re-authorization per affected connection on your side. This can be done by navigating to the impacted workflow, and either refreshing the Salesforce credential in one of the impacted workflows, or creating a new credential and saving.
NOTE: If the Salesforce Outbound Message connection is broken, triggering the workflows will stop with no apparent message on the Qualtrics side and no new runs will be visible in the Run History. There will be a gap between current time and last execution. The failed Outbound Messages can be observed in Salesforce: Setup -> Environments -> Monitoring -> Outbound Messages, see failed outbound messages.