FormAssembly Incident History

1. resolvedOct 23 · 17:20 UTC

   This incident has been resolved.

Reported by FormAssembly on their status page.

1. resolvedOct 19 · 18:37 UTC

   This incident has been resolved. We identified the source of the automated traffic and put protective measures in place; submission volume has since returned to normal across all affected environments. We are continuing to monitor for any recurrence — if you see a new wave of unexpected submissions, please contact Support. As an added layer of protection, we recommend enabling the anti-spam features available in your form settings. See Preventing Spam Responses for details, or reach out to Support if you’d like help applying them. Update — October 20, 2026 Sources have been blocked and behavior-based detection is in place; new attempts are now caught and blocked the same day. Because this originates from an outside party, further attempts remain possible, and we are continuing to monitor and respond. We recommend enabling ALTCHA or CAPTCHA on public forms.

Reported by FormAssembly on their status page.

1. resolvedOct 12 · 18:53 UTC

   We have reauthorized the Salesforce connections that were disconnected during this incident. 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 9 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.

Reported by FormAssembly on their status page.

1. resolvedOct 6 · 17:26 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.

Reported by FormAssembly on their status page.

1. resolvedSep 30 · 18:18 UTC

   This incident has been resolved.

Reported by FormAssembly on their status page.

1. resolvedSep 23 · 20:00 UTC

   Timeline: September 23, 2026, ~16:00 UTC — A change to our Salesforce connector introduced an issue causing some form submissions to intermittently fail to connect to Salesforce, showing a generic connection error. The number of affected accounts grew over the following two weeks. October 7, 2026 — The underlying change was identified and reverted as part of a scheduled release, deployed in stages across all production regions with no issues observed. Salesforce connector submissions are now completing normally. Resolution: The faulty change has been fully rolled back. Customer guidance: If you saw “Connection - Error connecting to Salesforce” on a form: Go to Preferences > External Authorizations and check the status of your Salesforce authorization. If the authorization shows as Valid, you do not need to reauthorize. Reprocess the affected responses instead. If the authorization shows as invalid or expired, reauthorize it once from the External Authorizations page. Don’t reauthorize from inside individual connectors. Salesforce limits the number of active authorizations per user. Responses submitted while the connector was failing were saved in FormAssembly and were not lost. To resend individual responses, see Resend a response through a connector. If you’re on a plan with bulk reprocessing, you can resend many responses at once. See Reprocessing responses in bulk.

Reported by FormAssembly on their status page.