Sep <var data-var='date'>30</var>, <var data-var='time'>14:18</var> EDT Resolved - This incident has been resolved. Sep <var data-var='date'>30</var>, <var data-var='time'>13:49</var> EDT Monitoring - 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.

Submission and Connector Errors for a Subset of Accounts

Sep <var data-var='date'>17</var>, <var data-var='time'>10:30</var> EDT Resolved - This incident has been resolved. Sep <var data-var='date'>16</var>, <var data-var='time'>20:57</var> EDT 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. Sep <var data-var='date'>16</var>, <var data-var='time'>18:43</var> EDT 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 Connector Authorization Issues Following Recent Salesforce Outage

Sep <var data-var='date'>16</var>, <var data-var='time'>15:55</var> EDT Resolved - 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 Sep <var data-var='date'>16</var>, <var data-var='time'>14:53</var> EDT 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. Sep <var data-var='date'>16</var>, <var data-var='time'>12:45</var> EDT Update - 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. Sep <var data-var='date'>16</var>, <var data-var='time'>10:45</var> EDT 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.

Salesforce Service Disruption

Aug <var data-var='date'>28</var>, <var data-var='time'>13:31</var> EDT Resolved - 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. Aug <var data-var='date'>28</var>, <var data-var='time'>13:00</var> EDT 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.

Form-level Salesforce Connector and Email Notifications Delayed Processing on Submission

Aug <var data-var='date'>24</var>, <var data-var='time'>18:55</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'>24</var>, <var data-var='time'>17:23</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>24</var>, <var data-var='time'>16:01</var> EDT Investigating - We are currently investigating reports of slowness and possible gateway errors. We will post more information as it becomes available.

Platform Slowness and Possible Gateway Errors

Aug <var data-var='date'>20</var>, <var data-var='time'>17:24</var> EDT Resolved - Resolved — This issue is resolved. Between August 18 at 1:03 PM ET and August 20 at 11:49 AM ET, files attached to Government Cloud form submissions were not saved due to a storage configuration issue introduced during a hosting architecture change. Form submissions completed and responses were saved; only the uploaded files were affected. Files uploaded during this window were not stored and cannot be recovered. They will need to be submitted again. All other response data is intact. Uploads have been working normally since August 20 at 11:49 AM ET, and we have verified successful uploads across multiple accounts. Customers with questions about specific responses should contact FormAssembly Support. Aug <var data-var='date'>20</var>, <var data-var='time'>11:19</var> EDT Identified - The team has identified an issue where submitting forms with a file upload field causes the submission to fail. The team is currently isolating a fix for the issue.

Gov Cloud accounts: File Uploads breaking responses

Aug <var data-var='date'>20</var>, <var data-var='time'>10:51</var> EDT Resolved - This incident has been resolved. Please reach out to support if you continue to run into any trouble. Aug <var data-var='date'>19</var>, <var data-var='time'>15:42</var> EDT Identified - 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. Aug <var data-var='date'>18</var>, <var data-var='time'>14:49</var> EDT Monitoring - 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. Aug <var data-var='date'>18</var>, <var data-var='time'>13:35</var> EDT Update - We are continuing to investigate the issue. Aug <var data-var='date'>18</var>, <var data-var='time'>12:03</var> EDT Investigating - 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.

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

Aug <var data-var='date'>19</var>, <var data-var='time'>13:41</var> EDT Resolved - This incident has been resolved. We identified and corrected the underlying issue, and Salesforce Marketing Cloud (SFMC) Prefill and Submit connectors are now loading and operating as expected. Affected forms are accessible again. Please note that a subset of responses submitted between 9:20 AM and 1:20 PM ET on August 19, 2026 may not have been sent to Salesforce Marketing Cloud and may need to be manually reprocessed. We recommend reviewing responses submitted during this window and reprocessing any that did not sync as expected. Thank you for your patience. Aug <var data-var='date'>19</var>, <var data-var='time'>13:26</var> EDT Monitoring - We've identified the cause of the issue affecting Salesforce Marketing Cloud (SFMC) Prefill and Submit connectors and have applied a fix. Connector configurations should now be loading normally, and affected forms should be accessible again. We're monitoring closely to confirm full recovery. Aug <var data-var='date'>19</var>, <var data-var='time'>13:12</var> EDT Investigating - We're investigating reports that Salesforce Marketing Cloud (SFMC) Prefill and Submit connector configurations are not loading. Forms that use the SFMC Prefill connector may currently be inaccessible. Our team is actively looking into the cause, and we'll share an update shortly.

Salesforce Marketing Cloud Connectors Unavailable

Aug <var data-var='date'>13</var>, <var data-var='time'>22:08</var> EDT Resolved - Delayed Salesforce Connector and Email Notification Processing on Form Submission has been resolved. Both the Salesforce Connector and email notifications are now running as expected. We apologize for any inconvenience caused and appreciate your patience. If you continue to experience issues, please contact support. Aug <var data-var='date'>13</var>, <var data-var='time'>18:09</var> EDT Monitoring - We identified a period of increased submission volume that resulted in delayed connector and email notification processing. The increased activity has subsided, and processing queues have now caught up. We have not identified any broader service issues and will continue to monitor the situation. Aug <var data-var='date'>13</var>, <var data-var='time'>16:54</var> EDT Investigating - We are currently investigating reports that the form-level Salesforce connector and form notifications are experiencing delayed processing upon form submission for some accounts. Our team is actively investigating the issue and will share additional updates as our investigation progresses. Update: Further investigation shows this is a delay in processing rather than a failure to process.

Aug <var data-var='date'> 7</var>, <var data-var='time'>14:30</var> EDT Resolved - Between approximately 2:45pm - 3pm ET a small segment of our Compliance Cloud accounts may have experienced temporary access loss to their forms and/or accounts. This was quickly identified and resolved by our team. There may also be a slight delay in purge jobs associated with this outage.

Compliance Cloud accounts/forms temporarily unavailable

Aug <var data-var='date'> 5</var>, <var data-var='time'>12:32</var> EDT Resolved - The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks. Jun <var data-var='date'>26</var>, <var data-var='time'>10:47</var> EDT Investigating - We have reopened our investigation into reports of connectivity issues from UK customers using BT and EE networks. Although BT previously confirmed that the underlying network issue had been resolved, we continue to receive reports from some customers who are still unable to access FormAssembly. We are working with BT to determine the cause of the continued reports. In the meantime, customers may be able to restore access by connecting through an alternative network, such as mobile data or a different ISP. For reference, our previous incident update is available here: https://status.formassembly.com/incidents/1cgbt78n7h3b We will continue to provide updates as we learn more.

Connectivity Issues for UK BT/EE Customers (Follow-up)

Jul <var data-var='date'>31</var>, <var data-var='time'>17:38</var> EDT Resolved - This incident has been resolved. Jul <var data-var='date'>30</var>, <var data-var='time'>18:41</var> EDT Monitoring - We’ve deployed changes addressing several contributing causes of the Salesforce connector authorization issues, and the number of new reports has decreased significantly. We’re continuing to monitor the situation closely and will provide another update as we confirm the stability of these changes. Jul <var data-var='date'>24</var>, <var data-var='time'>18:05</var> EDT Investigating - We are currently investigating reports of broken or invalid Salesforce authorizations affecting some accounts. Follow the steps below to restore the connection: - Before reauthorizing, check how many active connections you currently have in Salesforce. Click your profile icon in the upper-right corner of Salesforce, then go to Settings > Manage Connections. - In the OAuth Apps table, check how many times FormAssembly Connector appears. Salesforce allows a maximum of five connections per connected app. - If you already have five FormAssembly Connector connections, revoke any connections with the lowest use count. This will free up a token and help prevent Salesforce from revoking a connection that is still actively being used. Next, return to FormAssembly. Hover over your username in the upper-right corner and select External Authorizations. Reauthorize any connections marked as invalid. - If you have fewer than five connections, hover over your username in the upper-right corner of FormAssembly and select External Authorizations. Then, reauthorize any connections marked as invalid. If you continue to run into issues, please contact our support team.

Salesforce Connector Authorization Issues

Jul <var data-var='date'>24</var>, <var data-var='time'>13:35</var> EDT Completed - The scheduled maintenance has been completed. Jul <var data-var='date'>20</var>, <var data-var='time'>15:38</var> EDT Update - Scheduled maintenance is still in progress. We will provide updates as necessary. Jul <var data-var='date'>20</var>, <var data-var='time'>13:35</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>20</var>, <var data-var='time'>13:30</var> EDT Scheduled - Status: Scheduled starting today, through the week Affected Feature: Salesforce Connected App / OAuth Authentication What's Changing To meet updated Salesforce security requirements, FormAssembly will be enabling the following settings on our Salesforce connected app: Phase 1 Refresh Token Rotation (RTR) — A new refresh token will be issued with each access token refresh. Proof Key for Code Exchange (PKCE) — An additional layer of protection for supported OAuth authorization flows. Refresh Token IP Allowlist Enforcement — Token refresh requests will be restricted to allowlisted IP addresses. Phase 2 (following Phase 1) Idle Refresh Token Expiration — Salesforce refresh tokens that have been inactive for 30 or more days will expire and require reauthorization. What to Expect We've completed thorough testing of these changes to help ensure a seamless experience for our customers. For most users, no action will be required. In some cases, you may be prompted to reauthorize your Salesforce connection in FormAssembly after the changes go live. This is a one-time action and takes just a few moments to complete. To get ahead of this, we recommend checking your External Authorizations page (accessible via your account menu) to review the status of your Salesforce connectors. If any show as unauthorized or disconnected, you can reauthorize them directly from that page. Step-by-step instructions are also available in our Resource Center https://help.formassembly.com/help/connect-to-salesforce#salesforce-authentication. We also recommend enabling downtime and processing error alerts for your forms so you're notified promptly of any issues. This can be configured within your general settings. https://help.formassembly.com/help/preferences#communications-from-formassembly. Need Help? If you notice any unexpected behavior with your Salesforce connection that you believe may be related to these changes, please don't hesitate to reach out to our Support team. We're happy to help.

Upcoming Security Enhancements to Salesforce Integration

Jun <var data-var='date'>24</var>, <var data-var='time'>17:47</var> EDT Resolved - The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks. Jun <var data-var='date'>16</var>, <var data-var='time'>15:20</var> EDT Investigating - We are aware of an issue affecting customers in the UK accessing FormAssembly via BT Internet Service Provider and its subsidiaries (including EE). Affected users may be unable to reach FormAssembly instances and forms. This issue appears to be network-specific. If you are affected, connecting via an alternative network (such as a mobile data connection or a different ISP) should restore access. Our team is actively investigating. We will provide updates as we learn more.

Connectivity Issues for UK BT/EE Customers

May <var data-var='date'>21</var>, <var data-var='time'>01:30</var> EDT Resolved - Earlier today, one of our sending IPs was listed on a third-party blocklist, causing some outbound email notifications to be blocked or delayed by recipient mail servers. The IP has since been delisted, and email delivery has returned to normal. We apologize for the disruption.

Email Notification Delivery Issue

May <var data-var='date'>20</var>, <var data-var='time'>15:30</var> EDT Resolved - This incident has been resolved. Please note that responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm. May <var data-var='date'>20</var>, <var data-var='time'>11:43</var> EDT Update - We are continuing to investigate this issue. May <var data-var='date'>20</var>, <var data-var='time'>11:41</var> EDT Investigating - Our team is currently investigating reports of loss of access to a small subset of Team and Enterprise accounts. We will update here with more information shortly.

Loss of Salesforce Connector on small subset of accounts

Apr <var data-var='date'>22</var>, <var data-var='time'>00:00</var> EDT Resolved - Between April 22 and May 18, 2026, an issue caused Form Analytics metrics to be recorded incorrectly, resulting in metrics detail loss for that period. Form submissions and response data were not affected. The issue has since been identified and resolved. Our team is actively working to recover form submission counts for the affected timeframe. Please note that other metrics, including form views, drop-offs, and bounced views, will not display data for the affected period. We sincerely apologize for the disruption.

Form Analytics Metrics Issue

Apr <var data-var='date'>17</var>, <var data-var='time'>00:30</var> EDT Resolved - Earlier this morning, some accounts hosted on our Sydney servers experienced errors when loading forms, including “There was a problem on our end trying to load forms” and “An unknown error occurred.” The issue has been resolved, and services have returned to normal. We will continue to monitor.

Form Loading Issues

Apr <var data-var='date'> 8</var>, <var data-var='time'>10:49</var> EDT Resolved - The issue affecting email notification delivery has been resolved. A temporary third-party blocklist listing was identified and removed. Email notifications are now functioning normally. If you continue to experience issues, please contact support. Apr <var data-var='date'> 7</var>, <var data-var='time'>19:56</var> EDT Monitoring - We have identified the cause of the email notification delivery issue as a temporary listing of one of our sending IPs on a third-party blocklist, which resulted in email rejections for some customers. The listing has since been removed, and we have not observed any new rejection logs since 2:21 PM ET. Email notifications should now be functioning normally. We are continuing to monitor the situation to ensure stability. We will provide another update once we confirm the issue is fully resolved. Apr <var data-var='date'> 7</var>, <var data-var='time'>15:35</var> EDT Investigating - Some customers are reporting that email notifications aren't being sent as expected upon form completion, and our team is investigating now. We will post more information as it becomes available.

Email Notifications

Mar <var data-var='date'>26</var>, <var data-var='time'>11:57</var> EDT Resolved - This incident has been resolved. Mar <var data-var='date'>26</var>, <var data-var='time'>11:18</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>26</var>, <var data-var='time'>10:50</var> EDT Investigating - We are investigating reports of inaccessible form lists affecting accounts in the Frankfurt region. We understand the disruption this may cause and are actively working to resolve it as quickly as possible. We will provide updates as more information becomes available.

Inaccessible Form Lists – Frankfurt Region

Feb <var data-var='date'>12</var>, <var data-var='time'>15:22</var> EST Resolved - This incident has been resolved. Feb <var data-var='date'>12</var>, <var data-var='time'>14:55</var> EST Monitoring - A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector. Feb <var data-var='date'>12</var>, <var data-var='time'>14:10</var> EST Investigating - We are currently investigating an issue impacting Microsoft Excel and Sharepoint connectors on the platform. At this time, customers who encounter connector errors are unable to successfully reconnect to Microsoft. Once the error appears, reconnection attempts are failing, and affected connectors remain blocked. Our team is actively working to identify the root cause and restore reconnection functionality as quickly as possible. We will provide updates here as soon as more information becomes available.

Microsoft Excel and Sharepoint Connector Reconnection Issue

Feb <var data-var='date'> 4</var>, <var data-var='time'>15:27</var> EST Resolved - The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored. Feb <var data-var='date'> 2</var>, <var data-var='time'>15:58</var> EST Identified - We have identified the cause of the issue impacting form submission redirects. Our engineering team is actively working on a fix, which will be implemented as soon as possible. We will continue to provide updates here as progress is made. Feb <var data-var='date'> 2</var>, <var data-var='time'>15:27</var> EST Investigating - We are currently investigating an issue where some form submissions are not redirecting respondents as expected after submission. Under normal circumstances, respondents are redirected back to the form if there is a validation or connector error, allowing them to correct their information and resubmit. If no errors occur, respondents are redirected to the configured thank-you page or redirect URL. Some submissions may remain on the response processing page and display a default confirmation message instead of submissions displaying potential errors. Our team is actively investigating the root cause of this issue. We will continue to post updates here as more information becomes available.

Some Form Submissions Not Redirecting Properly

Jan <var data-var='date'>29</var>, <var data-var='time'>09:51</var> EST Resolved - We experienced processing delays with Salesforce connectors in the London region due to increased system load. Our team has upgraded system capacity and the issue is now resolved. All connectors are operating normally.

Salesforce Connector - London Region - RESOLVED

Jan <var data-var='date'>23</var>, <var data-var='time'>14:11</var> EST Resolved - This incident has been resolved. Please reach out to support@formassembly.com if you run into any further issues. Jan <var data-var='date'>22</var>, <var data-var='time'>10:00</var> EST Identified - We confirmed a secondary issue related to yeseterday's SAML concern where SAML authenticated forms are not preserving URL query parameters after authentication. The team has identified the root cause and is working to resolve the issue. Additional details will be provided here as they become available.

SAML authenticated forms not preserving URL query parameters after authenticated

Jan <var data-var='date'>21</var>, <var data-var='time'>18:02</var> EST Resolved - The issue impacting SAML authentication has been fully resolved. Respondents can now access SAML-authenticated forms as expected, and SAML-based login is functioning normally. Our team has confirmed service restoration and is continuing to monitor the system to ensure stability. Thank you for your patience while we worked to resolve this issue. Jan <var data-var='date'>21</var>, <var data-var='time'>16:52</var> EST Identified - The issue impacting SAML authentication has been identified, and a fix is currently being implemented. Some respondents may still be unable to access SAML-authenticated forms, and SAML-based login may continue to be affected during this time. Our engineering team is actively deploying the fix and monitoring the situation closely. We will provide another update once the fix has been fully applied and we’ve confirmed service restoration. Jan <var data-var='date'>21</var>, <var data-var='time'>15:40</var> EST Investigating - We are currently investigating an issue that is impacting SAML authentication. At this time, some respondents are unable to access SAML-authenticated forms. This issue may also affect SAML-based login. Our engineering team is actively working to identify the root cause and implement a fix. We will provide updates as more information becomes available.

Is FormAssembly down?

FormAssembly status is UNDER MAINTENANCE

Components with issues

Lastest published events

Submission and Connector Errors for a Subset of Accounts

Salesforce Connector Authorization Issues Following Recent Salesforce Outage

Salesforce Service Disruption

FormAssembly Services, Components and Regions

Recent FormAssembly events

Submission and Connector Errors for a Subset of Accounts

Salesforce Connector Authorization Issues Following Recent Salesforce Outage

Salesforce Service Disruption

Form-level Salesforce Connector and Email Notifications Delayed Processing on Submission

Platform Slowness and Possible Gateway Errors

Gov Cloud accounts: File Uploads breaking responses