Is FormAssembly down?

Beginning at about 02:30 UTC on October 23 (10:30 PM ET on October 22), some forms with a Salesforce connection began failing with “Error connecting to Salesforce.” This was related to an issue on the Salesforce side, which Salesforce has since resolved: https://status.salesforce.com/incidents/20004512 Authorizations that were affected will not recover on their own and need to be reauthorized. Until then, affected forms may not send data to Salesforce or pull data from it, forms that use the Salesforce Prefill connector may not be prefilled, and dynamic picklists may fail to populate. Your Salesforce authorization may still show as Valid in your account even though it is affected. To restore your connection: • Open an affected form’s Salesforce connector and note which authorization it uses. • Hover over your username in the top right and select External Authorizations. • Select Reauthorize on that authorization. Reauthorize once per Salesforce user, from this page, rather than from each individual connector. 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.

This incident has been resolved.

We are investigating increased reports of spam hitting a small segment of forms. Some customers may be seeing unwanted spam responses on their forms. In the meantime, you can reduce spam on your forms by turning on spam protection. Learn more: https://help.formassembly.com/help/preventing-spam-responses” We will share an update as soon as we have more information.

We are continuing to investigate this issue.

We've applied a block that has significantly reduced this traffic. We're continuing to monitor and refine the block.If you see unexpected responses in your account, you can safely delete them. If you need help, contact Support.

This incident has been resolved. We identified the source of the automated traffic and put protective measures in place on October 17; submission volume has since returned to normal across all affected environments. We are continuing to monitor for any recurrence — if you see a new wave of unexpected submissions, please contact Support. As an added layer of protection, we recommend enabling the anti-spam features available in your form settings. See Preventing Spam Responses for details, or reach out to Support if you’d like help applying them.

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.

We have reauthorized the Salesforce connections that were disconnected during this incident. The exception is connections that customers had already reconnected themselves. What this means for you: - No action is needed to restore your Salesforce authorization. Connectors and dynamic picklists that depend on it should be working again. - Form responses submitted while your connector was failing were saved in FormAssembly and were not lost. If you haven't already, reprocess them from the connector log. - If you reauthorized on your own after October 3 and your connectors are working, no further action is needed. Current status - We are monitoring all affected accounts to confirm the reauthorizations worked. If we detect an authorization that is still failing, we will contact you directly. - We are still establishing the root cause. We will share more once our analysis is complete. If you still see "Error connecting to Salesforce" or "Authorization is no longer valid," please contact FormAssembly Support. If you reauthorize manually, do it once per Salesforce user from Preferences > External Authorizations, not form by form. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit.

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.

We have reauthorized the Salesforce connections that were disconnected between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET). The exception is connections that customers had already reconnected themselves. What this means for you: - No action is needed to restore your Salesforce authorization. Connectors and dynamic picklists that depend on it should be working again. - Form responses submitted while your connector was failing were saved in FormAssembly and were not lost. If you haven't already, reprocess them from the connector log. - If you reauthorized on your own after October 3 and your connectors are working, no further action is needed. Current status - We are monitoring all affected accounts to confirm the reauthorizations worked. If we detect an authorization that is still failing, we will contact you directly. - We are still establishing the root cause. We will share more once our analysis is complete. If you still see "Error connecting to Salesforce" or "Authorization is no longer valid," please contact FormAssembly Support. If you reauthorize manually, do it once per Salesforce user from Preferences > External Authorizations, not form by form. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit.

Between approximately 10:30 AM and 12:40 PM ET, a small number of customers experienced errors during our scheduled release. Affected actions included submitting a form, editing or finalizing a response, resending a response, and running workflow connectors and form-level connectors. The issue was resolved once the release was fully deployed, and we have confirmed that no new errors have occurred. If a workflow connector step failed during this window, you can replay the step from the workflow response. https://help.formassembly.com/help/replay#replaying-a-connector-step If a form-level connector failed, you can reprocess the response to send it through your connectors again. https://help.formassembly.com/help/responses#reprocess-a-response If a payment connector failed, please reopen the response so the respondent can re-enter their payment information. and submit the form again. https://help.formassembly.com/help/responses#reopen-response We apologize for the disruption this caused.

This incident has been resolved.