FormAssembly incident

Salesforce Connector Authorization Issues

Minor Resolved View vendor source →

FormAssembly experienced a minor incident on July 24, 2026 affecting Salesforce Connector and Salesforce Prefill Connector, lasting 6d 23h. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2026, 10:05 PM UTC
Resolved
Jul 31, 2026, 09:38 PM UTC
Duration
6d 23h
Detected by Pingoru
Jul 24, 2026, 10:05 PM UTC

Affected components

Salesforce ConnectorSalesforce Prefill Connector

Update timeline

  1. investigating Jul 24, 2026, 10:05 PM UTC

    We are currently investigating reports of broken or invalid Salesforce authorizations affecting some accounts. Follow the steps below to restore the connection: - Before reauthorizing, check how many active connections you currently have in Salesforce. Click your profile icon in the upper-right corner of Salesforce, then go to Settings > Manage Connections. - In the OAuth Apps table, check how many times FormAssembly Connector appears. Salesforce allows a maximum of five connections per connected app. - If you already have five FormAssembly Connector connections, revoke any connections with the lowest use count. This will free up a token and help prevent Salesforce from revoking a connection that is still actively being used. Next, return to FormAssembly. Hover over your username in the upper-right corner and select External Authorizations. Reauthorize any connections marked as invalid. - If you have fewer than five connections, hover over your username in the upper-right corner of FormAssembly and select External Authorizations. Then, reauthorize any connections marked as invalid. If you continue to run into issues, please contact our support team.

  2. monitoring Jul 30, 2026, 10:41 PM UTC

    We’ve deployed changes addressing several contributing causes of the Salesforce connector authorization issues, and the number of new reports has decreased significantly. We’re continuing to monitor the situation closely and will provide another update as we confirm the stability of these changes.

  3. resolved Jul 31, 2026, 09:38 PM UTC

    This incident has been resolved.