Live / FormAssembly / Incident
FormAssembly: Salesforce connector authorizations invalidated on October 3 - small subset of account across the platform
FormAssembly · formassembly.comMinor incidentResolved2026-10-06 17:26 UTC
Public — what happened
Summary
FormAssembly said that during a window early on October 3 (00:31 to 05:25 UTC), Salesforce turned down some of its token refresh requests, which caused Salesforce authorizations for a very small number of customer accounts in all regions to be flagged as invalid. The company said Salesforce connectors and dynamic picklists relying on those authorizations kept failing with connection or authorization errors until customers reconnected. It posted the issue on October 6 at 14:27 UTC, advised affected users to reauthorize once per Salesforce user from the External Authorizations settings page, and said form submissions made during the failures were kept and could be reprocessed. The incident was marked resolved later that day at 17:26.
Affected
FormAssembly Professional/Premier, FormAssembly Essentials, FormAssembly Team, FormAssembly Basic, FormAssembly Enterprise, FormAssembly Compliance
Timeline
- Started — 2026-10-06 14:27 UTC
- Identified — 2026-10-06 14:27 UTC
- Resolved — 2026-10-06 17:26 UTC · 2h 59m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach FormAssembly against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for FormAssembly: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the FormAssembly report →
More from FormAssembly
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.