Is FormAssembly down?

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.