FormAssembly incident

Form-Level Salesforce Connector and Email Notifications Not Processing Upon Submission

Minor Resolved View vendor source →

FormAssembly experienced a minor incident on August 18, 2026 affecting Salesforce Connector and Emails, lasting 1d 22h. The incident has been resolved; the full update timeline is below.

Started
Aug 18, 2026, 04:03 PM UTC
Resolved
Aug 20, 2026, 02:51 PM UTC
Duration
1d 22h
Detected by Pingoru
Aug 18, 2026, 04:03 PM UTC

Affected components

Salesforce ConnectorEmails

Update timeline

  1. investigating Aug 18, 2026, 04:03 PM UTC

    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.

  2. investigating Aug 18, 2026, 05:35 PM UTC

    We are continuing to investigate the issue.

  3. monitoring Aug 18, 2026, 06:49 PM UTC

    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.

  4. identified Aug 19, 2026, 07:42 PM UTC

    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.

  5. resolved Aug 20, 2026, 02:51 PM UTC

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