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
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.
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
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.
The team has identified an issue where submitting forms with a file upload field causes the submission to fail. The team is currently isolating a fix for the issue.
Salesforce Marketing Cloud Connectors Unavailable
majorSource not attested
Last archived state: resolved
View archived record details
Salesforce Marketing Cloud Connector
monitoring
We've identified the cause of the issue affecting Salesforce Marketing Cloud (SFMC) Prefill and Submit connectors and have applied a fix. Connector configurations should now be loading normally, and affected forms should be accessible again. We're monitoring closely to confirm full recovery.
investigating
We're investigating reports that Salesforce Marketing Cloud (SFMC) Prefill and Submit connector configurations are not loading. Forms that use the SFMC Prefill connector may currently be inaccessible. Our team is actively looking into the cause, and we'll share an update shortly.
Form-Level Salesforce Connector and Email Notifications Not Processing Upon Submission
minorSource not attested
Last archived state: resolved
View archived record details
Salesforce ConnectorEmails
identified
While we hoped the yesterdays response would be a complete fix, customers continue to experience intermittent issues with the delays. The team has identified the potential cause and is actively working on that fix. We will continue to post here when new information is available.
monitoring
We’ve mitigated the processing delays affecting Salesforce connector submissions and form notifications. Processing has returned to normal, and affected submissions and notifications should now be going through as expected.
Clarification: This was a processing delay, not a failure. Affected submissions and notifications were queued and should complete automatically without needing to be reprocessed.
Potential duplicate records: If you manually reprocessed a submission while it was delayed...
investigating
We are continuing to investigate the issue.
investigating
We are investigating reports that the form-level Salesforce connector and form notifications are not processing upon form submission for a subset of accounts.
We are actively investigating and will provide updates as more information becomes available.
Form-level Salesforce Connector and Email Notifications Delayed Processing on Submission
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We identified a period of increased submission volume that resulted in delayed connector and email notification processing. The increased activity has subsided, and processing queues have now caught up.
We have not identified any broader service issues and will continue to monitor the situation.
investigating
We are currently investigating reports that the form-level Salesforce connector and form notifications are experiencing delayed processing upon form submission for some accounts.
Our team is actively investigating the issue and will share additional updates as our investigation progresses.
Update: Further investigation shows this is a delay in processing rather than a failure to process.
July 2026
Salesforce Connector Authorization Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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 con...
June 2026
Connectivity Issues for UK BT/EE Customers (Follow-up)
Source not attested
Last archived state: resolved
View archived record details
investigating
We have reopened our investigation into reports of connectivity issues from UK customers using BT and EE networks.
Although BT previously confirmed that the underlying network issue had been resolved, we continue to receive reports from some customers who are still unable to access FormAssembly. We are working with BT to determine the cause of the continued reports.
In the meantime, customers may be able to restore access by connecting through an alternative network, such as mobile data or ...
Connectivity Issues for UK BT/EE Customers
Source not attested
Last archived state: resolved
View archived record details
investigating
We are aware of an issue affecting customers in the UK accessing FormAssembly via BT Internet Service Provider and its subsidiaries (including EE). Affected users may be unable to reach FormAssembly instances and forms.
This issue appears to be network-specific. If you are affected, connecting via an alternative network (such as a mobile data connection or a different ISP) should restore access.
Our team is actively investigating. We will provide updates as we learn more.
May 2026
Loss of Salesforce Connector on small subset of accounts
Source not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
Our team is currently investigating reports of loss of access to a small subset of Team and Enterprise accounts. We will update here with more information shortly.
April 2026
Email Notifications
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the cause of the email notification delivery issue as a temporary listing of one of our sending IPs on a third-party blocklist, which resulted in email rejections for some customers.
The listing has since been removed, and we have not observed any new rejection logs since 2:21 PM ET. Email notifications should now be functioning normally.
We are continuing to monitor the situation to ensure stability. We will provide another update once we confirm the issue is fully resol...
investigating
Some customers are reporting that email notifications aren't being sent as expected upon form completion, and our team is investigating now.
We will post more information as it becomes available.
