Salesforce Service Disruption

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

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.

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.

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.