Increased Spam Submissions on Some Forms
Investigating - We are investigating increased reports of spam hitting a small segment of forms. Some customers may be seeing unwanted spam responses on their forms.

In the meantime, you can reduce spam on your forms by turning on spam protection. Learn more: https://help.formassembly.com/help/preventing-spam-responses

We will share an update as soon as we have more information.
Oct 17, 2026 - 15:08 EDT

About This Site

Welcome to FormAssembly's status page, a place for real-time information on system performance, status and security. If there are any interruptions in service, a note will be posted here. Thank you for choosing FormAssembly!

Uptime over the past 90 days. View historical uptime.
FormAssembly.com Operational
API Operational
FormAssembly Professional/Premier Operational
FormAssembly Essentials Operational
FormAssembly Team Operational
FormAssembly Basic Operational
FormAssembly Enterprise Operational
FormAssembly Compliance Operational
FormAssembly Government Operational
Salesforce Operational
Salesforce Connector Operational
Salesforce Prefill Connector Operational
Salesforce Marketing Cloud Connector Operational
Autosuggest service Operational
Emails Operational
Background services Operational
Support Live Chat Under Maintenance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 17, 2026

Unresolved incident: Increased Spam Submissions on Some Forms.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

No incidents reported.

Oct 14, 2026

No incidents reported.

Oct 13, 2026

No incidents reported.

Oct 12, 2026

Salesforce Connector Authorization Errors
Resolved - 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.
Oct 12, 14:53 EDT
Identified - Beginning at about 21:30 UTC on October 9 (5:30 PM ET), some forms with a Salesforce connection began failing with “Error connecting to Salesforce” or “Authorization is no longer valid.” Affected forms may not send data to Salesforce or pull data from it. Forms that use Salesforce Prefill connector may not be prefilled, and dynamic picklists may not display their values.

To restore your connection: click your username in the top right and select External Authorizations. 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. Once the authorization is restored, you can reprocess them from the connector log: https://help.formassembly.com/help/resend-response-through-a-connector#resending-responses-from-the-connector-log

If a Salesforce step in a workflow failed, you can replay it from the workflow response: https://help.formassembly.com/help/replay#replaying-a-connector-step

We apologize for the disruption this is causing.
Oct 12, 10:28 EDT

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

No incidents reported.

Oct 6, 2026

Salesforce connector authorizations invalidated on October 3 - small subset of account across the platform
Resolved - 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.
Oct 6, 13:26 EDT
Identified - 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.
Oct 6, 10:27 EDT

Oct 5, 2026

No incidents reported.

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage