New Multi-region uptime checks and custom-domain status pages

FormAssembly Outage History

Daily provider-status observations and published incident history for FormAssembly.

Under maintenance

FormAssembly is reporting under maintenance. Verified . Official provider source.

Looking for an update now? Check the current status, or follow FormAssembly for future changes.

Building verified history 4 of 24 verified daily observations collected. A percentage will appear after the minimum coverage threshold is met.

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Salesforce Connector Authorization Errors
minor Observed active window 4h 26m

View incident details and source

Started:

Salesforce Connector Salesforce Prefill Connector
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.
Salesforce connector authorizations invalidated on October 3 - small subset of account across the platform
minor Observed active window 3h 2m

View incident details and source

Started:

FormAssembly Professional/Premier FormAssembly Essentials FormAssembly Team FormAssembly Basic FormAssembly Enterprise FormAssembly Compliance
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.
September 2026
Salesforce Service Disruption
minor Observed active window 5h 14m

View incident details and source

Started:

Salesforce Connector Salesforce Prefill Connector Salesforce Marketing Cloud Connector
monitoring
Salesforce reports that service telemetry is healthy and that their review has not confirmed any ongoing customer impact from this incident. Salesforce has not yet declared the incident resolved — they are verifying that the existing mitigation remains active across all affected Hyperforce environments and applying targeted updates where their automated process did not complete. If you have affected responses or workflow steps, you can begin reprocessing. We'd suggest starting with a small batch to confirm your Salesforce instance is accepting requests normally before working through the rest: Reprocess form responses: https://help.formassembly.com/help/responses#reprocess-a-response Replay workflow connector steps: https://help.formassembly.com/help/replay#replaying-a-connector-step Please continue to review before reprocessing in bulk. As noted in our earlier update, responses submitted during the disruption may have been saved with missing or empty values from prefill, lookup, or dynamic picklist connectors — including hidden fields such as Salesforce record IDs. Reprocessing and replay cannot restore values that never populated, so records may be incomplete, fail to match the intended record, or create duplicates. Note also that replay runs against your current connector configuration, and replaying a form step re-executes all subsequent steps in the workflow. Salesforce's incident page remains the best source for instance-level status: https://status.salesforce.com/incidents/20004433 We will post a final update once Salesforce declares the incident resolved.
investigating
No change to report. Salesforce's incident remains ongoing and we have not received an updated timeline from Salesforce. Impact and guidance are unchanged from our initial update above. FormAssembly continues to operate normally. Salesforce's incident page remains the best source for instance-level status: https://status.salesforce.com/incidents/20004433 We will post another update within 1-2 hours, or sooner if Salesforce's status changes.
investigating
Salesforce is currently experiencing a service disruption affecting a number of its instances. Impact is limited to customers whose Salesforce instance is affected. To check whether yours is included, visit https://status.salesforce.com/incidents/20004433 and look up your instance. FormAssembly itself is operating normally. Form building and form publishing are unaffected, and responses are being collected and saved as usual. If your Salesforce instance is affected, you may see: -Errors or delays on Salesforce Connector steps in forms and workflows -Prefill and lookup connectors failing or returning incomplete data -Dynamic picklists failing to populate or loading incomplete values -Intermittent issues with Salesforce-based single sign-on Two things to be aware of: 1. We cannot guarantee that data captured during this window is complete. Because prefill, lookup, and dynamic picklist connectors run while a form is loading, responses submitted during the disruption may have been saved with missing or empty values — including hidden fields such as Salesforce record IDs, and picklist selections that never loaded. Reprocessing and replay re-run the connector against the data as it was saved, so they cannot restore values that failed to populate at submission time. Records may therefore be incomplete, fail to match the intended record, or create duplicates. 2. Failed connector runs will not resend automatically. Once Salesforce service is restored, you will need to take action for that data to reach Salesforce: Form responses — reprocess the affected responses: https://help.formassembly.com/help/responses#reprocess-a-response Workflow connector steps — replay the affected steps: https://help.formassembly.com/help/replay#replaying-a-connector-step We recommend reviewing responses submitted during this window before reprocessing or replaying, rather than acting in bulk, and waiting until Salesforce confirms recovery for your instance so that retries don't fail again. Note that replay runs against your current connector configuration, and replaying a form step re-executes all subsequent steps in the workflow. We are tracking Salesforce's incident and will post another update within 1-2 hours.
August 2026
Form-level Salesforce Connector and Email Notifications Delayed Processing on Submission
minor Observed active window 34m

View incident details and source

Started:

Salesforce Connector Emails
investigating
We are currently investigating reports of delayed processing affecting the form-level Salesforce connector and form notifications after form submission for some accounts. We apologize for any inconvenience this may be causing. We will provide updates as more information becomes available.

Legacy Incident Archive

11 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

March 2026
Inaccessible Form Lists – Frankfurt Region
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating reports of inaccessible form lists affecting accounts in the Frankfurt region. We understand the disruption this may cause and are actively working to resolve it as quickly as possible. We will provide updates as more information becomes available.
Get alerts for FormAssembly Subscribe to the provider incident feed Browse all services