FormAssembly Outage History

A fix has been implemented, and email notifications should now be sending as expected. Affected responses may need to be reprocessed to trigger the email notifications. https://help.formassembly.com/help/responses#reprocess-a-response

This incident has been resolved.

Starting on April 16 at 12:30 pm ET, we identified an issue that may have affected some workflow submissions following a recent product release. Workflow responses that were saved prior to the release, or started during a brief window afterward may have failed to complete. In both cases, workflow execution could become stuck at the email step. The release has since been rolled back to prevent further impact. We recommend replaying any affected submissions to unblock them. https://help.formassembly.com/help/replay If you need assistance, please don’t hesitate to reach out to our support team.

Our Live Agent Chat has temporarily been taken offline as we update the platform in hopes of improved performance. Please bear with us during this upgrade. As always, you can reach out to support team at [email protected] for help with any issues. Chat is back up and running!

A fix has been implemented, and file uploads should now be sending to Salesforce as expected. This incident was resolved at 9:20 PM EST.

A fix has been implemented. Salesforce Sandbox authorizations should now be working as expected. This incident was resolved at 3:27 PM EST.

This incident has been resolved.

This incident was resolved at approximately 6:46 PM ET. All missing data from December 19 to December 23 is now present and visible in the Form Analytics charts.

The team has identified the issue and implemented a fix. The forms list and individual forms should now be accessible and functioning as expected.

At approximately 12:30 pm on November 7th the team implemented a new feature aiding the speed of external exports on Compliance (Legacy), Enterprise (Legacy), Essentials, Team - during this switch over we encountered issues with exports in process. This issue was identified and resolved. If your team continues to run into any issues with the export - please first try deleting and re-processing the export. If the issue persists after that, please contact [email protected] with a link to the form with which you're currently.

A fix has been implemented. This incident has been resolved and all legacy workflows should be working as expected.

This incident has been resolved, and functionality has been restored to forms, workflows, and the Admin Dashboard. If you experience any further issues, please contact our support team at [email protected]

A segment of accounts reported issues with their Email Notifications and After Submit Salesforce connector not running since 09/20/2024 at approximately 2:20 PM EST. This incident has been resolved as of 09/23/2024 at approximately 2:00 PM EST. Currently, Notifications and After Submit Salesforce connectors are running as expected.

Starting on August 5th, a small subset of Essentials, Team, & Enterprise accounts experienced issues accessing the response report page and response pages for certain forms. We identified the root cause and implemented a fix on August 23rd, which has restored access for the majority of affected accounts.

This incident has been resolved.

We are seeing some reports of customers that are not able to log into their accounts, some of which are also seeing that forms are not correct, as though the wrong form is showing. This issue has since been resolved.

Our team is aware of an issue auto-formatting with a mask and currently have a ticket in place so that we can work on a resolution. However, in the meantime we do have a quick workaround that should help you get moving forward quickly: Access your form in the Form Builder. Click on the field that is encountering this issue and then on "Options". Under the Validation Rules section, remove the character limit. When a field uses Auto-Format with a mask, the character limit is already enforced based on the mask used (e.g. ###-### only allows 6 digits). Save your form. Please reach out to our support team should you need further assistance.

Beginning June 2nd, Form Analytics ceased working as expected across the accounts listed above who have the Analytics permission enabled. The issue was discovered and reported June 28th. It was resolved the morning of July 1st.

Reports of 404 errors on form submissions were reported on a small subset of Essentials, Teams, Enterprise & Fed accounts. The team quickly identified and resolved the issue for Essentials, Teams & Enterprise accounts on 6/30/2024 at approximately 1pm ET. The issue was resolved for the affected subset of Fed accounts on 7/1/2024 at approximately 10:45am ET.

On Thursday, June 20, 2024, a number of clients observed a Service Temporarily Unavailable error in their Salesforce connectors. This issue was caused by a problem on the Salesforce platform rather than with FormAssembly. Although it appears to have been resolved, please refer to the Salesforce status page for further updates. If necessary, you can resubmit your responses to trigger the Connector to run again.