Formassembly outage history

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.

The delayed processing affecting email notifications and Salesforce connectors has been resolved. Affected submissions were processed successfully after a delay. We’ve confirmed that both notifications and connectors are now processing normally.

We are currently investigating reports of slowness and possible gateway errors. We will post more information as it becomes available.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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.

Resolved — This issue is resolved. Between August 18 at 1:03 PM ET and August 20 at 11:49 AM ET, files attached to Government Cloud form submissions were not saved due to a storage configuration issue introduced during a hosting architecture change. Form submissions completed and responses were saved; only the uploaded files were affected. Files uploaded during this window were not stored and cannot be recovered. They will need to be submitted again. All other response data is intact. Uploads have been working normally since August 20 at 11:49 AM ET, and we have verified successful uploads across multiple accounts. Customers with questions about specific responses should contact FormAssembly Support.

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.

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.

This incident has been resolved. We identified and corrected the underlying issue, and Salesforce Marketing Cloud (SFMC) Prefill and Submit connectors are now loading and operating as expected. Affected forms are accessible again. Please note that a subset of responses submitted between 9:20 AM and 1:20 PM ET on August 19, 2026 may not have been sent to Salesforce Marketing Cloud and may need to be manually reprocessed. We recommend reviewing responses submitted during this window and reprocessing any that did not sync as expected. Thank you for your patience.

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.

We are continuing to investigate the issue.

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, you may see a duplicate record in Salesforce—one from the original submission and one from the reprocessing attempt. We recommend reviewing recently reprocessed submissions for duplicates.

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.

This incident has been resolved. Please reach out to support if you continue to run into any trouble.

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.

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.

Delayed Salesforce Connector and Email Notification Processing on Form Submission has been resolved. Both the Salesforce Connector and email notifications are now running as expected. We apologize for any inconvenience caused and appreciate your patience. If you continue to experience issues, please contact support.

Between approximately 2:45pm - 3pm ET a small segment of our Compliance Cloud accounts may have experienced temporary access loss to their forms and/or accounts. This was quickly identified and resolved by our team. There may also be a slight delay in purge jobs associated with this outage.

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 connected app. - If you already have five FormAssembly Connector connections, revoke any connections with the lowest use count. This will free up a token and help prevent Salesforce from revoking a connection that is still actively being used. Next, return to FormAssembly. Hover over your username in the upper-right corner and select External Authorizations. Reauthorize any connections marked as invalid. - If you have fewer than five connections, hover over your username in the upper-right corner of FormAssembly and select External Authorizations. Then, reauthorize any connections marked as invalid. If you continue to run into issues, please contact our support team.

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.

This incident has been resolved.

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 a different ISP. For reference, our previous incident update is available here: https://status.formassembly.com/incidents/1cgbt78n7h3b We will continue to provide updates as we learn more.

The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.

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.

The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.

Earlier today, one of our sending IPs was listed on a third-party blocklist, causing some outbound email notifications to be blocked or delayed by recipient mail servers. The IP has since been delisted, and email delivery has returned to normal. We apologize for the disruption.

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.

We are continuing to investigate this issue.

This incident has been resolved. Please note that responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.

**Update:** We previously marked this incident as resolved, but we have since identified additional accounts that may be affected. Our team is actively investigating and working to restore access. We apologize for the confusion and will continue to provide updates here as we learn more. As a reminder, responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.

Between April 22 and May 18, 2026, an issue caused Form Analytics metrics to be recorded incorrectly, resulting in metrics detail loss for that period. Form submissions and response data were not affected. The issue has since been identified and resolved. Our team is actively working to recover form submission counts for the affected timeframe. Please note that other metrics, including form views, drop-offs, and bounced views, will not display data for the affected period. We sincerely apologize for the disruption.

Earlier this morning, some accounts hosted on our Sydney servers experienced errors when loading forms, including “There was a problem on our end trying to load forms” and “An unknown error occurred.” The issue has been resolved, and services have returned to normal. We will continue to monitor.

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.

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 resolved.

The issue affecting email notification delivery has been resolved. A temporary third-party blocklist listing was identified and removed. Email notifications are now functioning normally. If you continue to experience issues, please contact support.

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.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating an issue impacting Microsoft Excel and Sharepoint connectors on the platform. At this time, customers who encounter connector errors are unable to successfully reconnect to Microsoft. Once the error appears, reconnection attempts are failing, and affected connectors remain blocked. Our team is actively working to identify the root cause and restore reconnection functionality as quickly as possible. We will provide updates here as soon as more information becomes available.

A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.

This incident has been resolved.

We are currently investigating an issue where some form submissions are not redirecting respondents as expected after submission. Under normal circumstances, respondents are redirected back to the form if there is a validation or connector error, allowing them to correct their information and resubmit. If no errors occur, respondents are redirected to the configured thank-you page or redirect URL. Some submissions may remain on the response processing page and display a default confirmation message instead of submissions displaying potential errors. Our team is actively investigating the root cause of this issue. We will continue to post updates here as more information becomes available.

We have identified the cause of the issue impacting form submission redirects. Our engineering team is actively working on a fix, which will be implemented as soon as possible. We will continue to provide updates here as progress is made.

The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.

We experienced processing delays with Salesforce connectors in the London region due to increased system load. Our team has upgraded system capacity and the issue is now resolved. All connectors are operating normally.

We confirmed a secondary issue related to yeseterday's SAML concern where SAML authenticated forms are not preserving URL query parameters after authentication. The team has identified the root cause and is working to resolve the issue. Additional details will be provided here as they become available.

This incident has been resolved. Please reach out to [email protected] if you run into any further issues.