FormAssembly incident

Salesforce connector authorizations invalidated on October 3 - small subset of account across the platform

Minor Resolved View vendor source →

FormAssembly experienced a minor incident on October 6, 2026 affecting FormAssembly Professional/Premier and FormAssembly Essentials and 1 more component, lasting 2h 58m. The incident has been resolved; the full update timeline is below.

Started
Oct 06, 2026, 02:27 PM UTC
Resolved
Oct 06, 2026, 05:26 PM UTC
Duration
2h 58m
Detected by Pingoru
Oct 06, 2026, 02:27 PM UTC

Affected components

FormAssembly Professional/PremierFormAssembly EssentialsFormAssembly TeamFormAssembly BasicFormAssembly EnterpriseFormAssembly Compliance

Update timeline

  1. identified Oct 06, 2026, 02:27 PM UTC

    Between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET), Salesforce rejected a set of token refresh requests from FormAssembly. As a result, Salesforce authorizations for a subset of customers across all regions were marked invalid in FormAssembly. Connectors and dynamic picklists that depend on those authorizations have been failing since then with "Error connecting to Salesforce" or "Authorization is no longer valid." Scope is currently being evaluated. Each identified account will be proactively identified. This affected a very small subset of accounts across the platform. If your Salesforce connectors are failing and you need them working now: Go to Preferences, then External Authorizations, and select Reauthorize on the affected Salesforce authorization. Reauthorize once per Salesforce user, from this page, rather than from each individual connector. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit and break working connections. Form responses submitted while the connector was failing were saved in FormAssembly and were not lost. Once the authorization is restored, reprocess them from the connector log. If you have reauthorized since October 3 and your connectors are working, no further action is needed.

  2. resolved Oct 06, 2026, 05:26 PM UTC

    We have reauthorized the Salesforce connections that were disconnected between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET). The exception is connections that customers had already reconnected themselves. What this means for you: - No action is needed to restore your Salesforce authorization. Connectors and dynamic picklists that depend on it should be working again. - Form responses submitted while your connector was failing were saved in FormAssembly and were not lost. If you haven't already, reprocess them from the connector log. - If you reauthorized on your own after October 3 and your connectors are working, no further action is needed. Current status - We are monitoring all affected accounts to confirm the reauthorizations worked. If we detect an authorization that is still failing, we will contact you directly. - We are still establishing the root cause. We will share more once our analysis is complete. If you still see "Error connecting to Salesforce" or "Authorization is no longer valid," please contact FormAssembly Support. If you reauthorize manually, do it once per Salesforce user from Preferences > External Authorizations, not form by form. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit.