Is FormAssembly Down?

This incident has been resolved. --- [2026-09-16T20:57:23.524-04:00] (monitoring) Our team has restored a number of Salesforce authorizations affected by the recent Salesforce service disruption. If your Salesforce Connector, Prefill Connector, or dynamic picklists are now working normally, no further action is needed. Some authorizations may still require manual reauthorization. If you're continuing to experience issues, please follow the troubleshooting steps in our previous update before reauthorizing your connection. --- [2026-09-16T18:43:32.352-04:00] (identified) Following the recent Salesforce service disruption (see our previous resolved incident: https://status.formassembly.com/incidents/0ksdl7t3kjvv), we’re seeing reports that one or more FormAssembly Salesforce authorizations may have been invalidated during the outage. If your Salesforce Connector, Prefill Connector, or dynamic picklists are still failing, please first check your FormAssembly External Authorizations page: 1. In FormAssembly, hover over your username in the upper-right corner and select External Authorizations. Check whether the Salesforce authorization used by the affected connector is marked as invalid. 2. If the authorization is invalid, do not reauthorize it yet. First, check how many active FormAssembly connections you currently have in Salesforce. Click your profile icon in the upper-right corner of Salesforce, then go to Settings > Manage Connections. 3. In the OAuth Apps table, check how many times FormAssembly Connector appears. 4. If you have fewer than five FormAssembly Connector connections, return to FormAssembly and reauthorize the invalid authorization. 5. If you already have five FormAssembly Connector connections, revoke a connection with the lowest use count first. This will free up an OAuth token and help prevent Salesforce from revoking another connection that may still be actively used. Then, return to FormAssembly and reauthorize the invalid authorization. We’ll continue to monitor the issue and post additional updates here as needed.

Salesforce has declared this incident resolved. Salesforce Prefill Connector and Submit Connector functionality has returned to normal, and FormAssembly continues to operate normally. If you have responses or workflow steps that failed during the disruption, you'll need to reprocess or replay them for that data to reach Salesforce: 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 review affected responses before reprocessing in bulk — see our earlier updates for details on potential incomplete data and duplicate records. Salesforce's incident page: https://status.salesforce.com/incidents/20004433 Update: If you're still experiencing Salesforce Connector, Prefill Connector, or dynamic picklist errors following this disruption, we've identified a related issue with Salesforce authorizations. Please see our new incident for details and next steps: https://status.formassembly.com/incidents/mmd81rfq65zq --- [2026-09-16T14:53:37.527-04:00] (monitoring) 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. --- [2026-09-16T12:45:16.643-04:00] (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. --- [2026-09-16T12:45:34.905-04:00] (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.

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. --- [2026-08-28T13:00:05.980-04:00] (investigating) 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.