FormAssembly Outage History

Started Oct 23, 2026, 04:38 PM UTC· resolved Oct 23, 2026, 05:20 PM UTC

1. identified Oct 23, 2026, 04:38 PM UTC

   Beginning at about 02:30 UTC on October 23 (10:30 PM ET on October 22), some forms with a Salesforce connection began failing with “Error connecting to Salesforce.” This was related to an issue on the Salesforce side, which Salesforce has since resolved: https://status.salesforce.com/incidents/20004512 Authorizations that were affected will not recover on their own and need to be reauthorized. Until then, affected forms may not send data to Salesforce or pull data from it, forms that use the Salesforce Prefill connector may not be prefilled, and dynamic picklists may fail to populate. Your Salesforce authorization may still show as Valid in your account even though it is affected. To restore your connection: • Open an affected form’s Salesforce connector and note which authorization it uses. • Hover over your username in the top right and select External Authorizations. • Select Reauthorize on that authorization. Reauthorize once per Salesforce user, from this page, rather than from each individual connector. Form responses submitted while the connector was failing were saved in FormAssembly. Once the authorization is restored, you can reprocess them from the connector log: https://help.formassembly.com/help/resend-response-through-a-connector#resending-responses-from-the-connector-log If a Salesforce step in a workflow failed, you can replay it from the workflow response: https://help.formassembly.com/help/replay#replaying-a-connector-step We apologize for the disruption this is causing.

2. resolved Oct 23, 2026, 05:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 17, 2026, 07:08 PM UTC· resolved Oct 19, 2026, 06:37 PM UTC

1. investigating Oct 17, 2026, 07:08 PM UTC

   We are investigating increased reports of spam hitting a small segment of forms. Some customers may be seeing unwanted spam responses on their forms. In the meantime, you can reduce spam on your forms by turning on spam protection. Learn more: https://help.formassembly.com/help/preventing-spam-responses” We will share an update as soon as we have more information.

2. investigating Oct 18, 2026, 09:37 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 19, 2026, 03:09 PM UTC

   We've applied a block that has significantly reduced this traffic. We're continuing to monitor and refine the block.If you see unexpected responses in your account, you can safely delete them. If you need help, contact Support.

4. resolved Oct 19, 2026, 06:37 PM UTC

   This incident has been resolved. We identified the source of the automated traffic and put protective measures in place on October 17; submission volume has since returned to normal across all affected environments. We are continuing to monitor for any recurrence — if you see a new wave of unexpected submissions, please contact Support. As an added layer of protection, we recommend enabling the anti-spam features available in your form settings. See Preventing Spam Responses for details, or reach out to Support if you’d like help applying them.

Read the full incident report →

Started Oct 06, 2026, 02:27 PM UTC· resolved Oct 06, 2026, 05:26 PM UTC

1. identified Oct 06, 2026, 02:27 PM UTC

   Between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET), Salesforce rejected a set of token refresh requests from FormAssembly. As a result, Salesforce authorizations for a subset of customers across all regions were marked invalid in FormAssembly. Connectors and dynamic picklists that depend on those authorizations have been failing since then with "Error connecting to Salesforce" or "Authorization is no longer valid." Scope is currently being evaluated. Each identified account will be proactively identified. This affected a very small subset of accounts across the platform. If your Salesforce connectors are failing and you need them working now: Go to Preferences, then External Authorizations, and select Reauthorize on the affected Salesforce authorization. Reauthorize once per Salesforce user, from this page, rather than from each individual connector. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit and break working connections. Form responses submitted while the connector was failing were saved in FormAssembly and were not lost. Once the authorization is restored, reprocess them from the connector log. If you have reauthorized since October 3 and your connectors are working, no further action is needed.

2. resolved Oct 06, 2026, 05:26 PM UTC

   We have reauthorized the Salesforce connections that were disconnected between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET). The exception is connections that customers had already reconnected themselves. What this means for you: - No action is needed to restore your Salesforce authorization. Connectors and dynamic picklists that depend on it should be working again. - Form responses submitted while your connector was failing were saved in FormAssembly and were not lost. If you haven't already, reprocess them from the connector log. - If you reauthorized on your own after October 3 and your connectors are working, no further action is needed. Current status - We are monitoring all affected accounts to confirm the reauthorizations worked. If we detect an authorization that is still failing, we will contact you directly. - We are still establishing the root cause. We will share more once our analysis is complete. If you still see "Error connecting to Salesforce" or "Authorization is no longer valid," please contact FormAssembly Support. If you reauthorize manually, do it once per Salesforce user from Preferences > External Authorizations, not form by form. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit.

Read the full incident report →

Started Sep 30, 2026, 05:49 PM UTC· resolved Sep 30, 2026, 06:18 PM UTC

1. monitoring Sep 30, 2026, 05:49 PM UTC

   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.

2. resolved Sep 30, 2026, 06:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 23, 2026, 08:00 PM UTC· resolved Sep 23, 2026, 08:00 PM UTC

1. resolved Oct 07, 2026, 07:35 PM UTC

   Timeline: September 23, 2026, ~16:00 UTC — A change to our Salesforce connector introduced an issue causing some form submissions to intermittently fail to connect to Salesforce, showing a generic connection error. The number of affected accounts grew over the following two weeks. October 7, 2026 — The underlying change was identified and reverted as part of a scheduled release, deployed in stages across all production regions with no issues observed. Salesforce connector submissions are now completing normally. Resolution: The faulty change has been fully rolled back. Customer guidance: If you saw “Connection - Error connecting to Salesforce” on a form: Go to Preferences > External Authorizations and check the status of your Salesforce authorization. If the authorization shows as Valid, you do not need to reauthorize. Reprocess the affected responses instead. If the authorization shows as invalid or expired, reauthorize it once from the External Authorizations page. Don’t reauthorize from inside individual connectors. Salesforce limits the number of active authorizations per user. Responses submitted while the connector was failing were saved in FormAssembly and were not lost. To resend individual responses, see Resend a response through a connector. If you’re on a plan with bulk reprocessing, you can resend many responses at once. See Reprocessing responses in bulk.

Read the full incident report →

Started Sep 16, 2026, 10:43 PM UTC· resolved Sep 17, 2026, 02:30 PM UTC

1. identified Sep 16, 2026, 10:43 PM UTC

   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.

2. monitoring Sep 17, 2026, 12:57 AM UTC

   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.

3. resolved Sep 17, 2026, 02:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 02:45 PM UTC· resolved Sep 16, 2026, 07:55 PM UTC

1. investigating Sep 16, 2026, 02:45 PM UTC

   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 60 minutes.

2. investigating Sep 16, 2026, 04:45 PM UTC

   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.

3. monitoring Sep 16, 2026, 06:53 PM UTC

   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.

4. resolved Sep 16, 2026, 07:55 PM UTC

   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

Read the full incident report →

Started Aug 28, 2026, 05:00 PM UTC· resolved Aug 28, 2026, 05:31 PM UTC

1. investigating Aug 28, 2026, 05:00 PM UTC

   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.

2. resolved Aug 28, 2026, 05:31 PM UTC

   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.

Read the full incident report →

Started Aug 24, 2026, 08:01 PM UTC· resolved Aug 24, 2026, 10:55 PM UTC

1. investigating Aug 24, 2026, 08:01 PM UTC

   We are currently investigating reports of slowness and possible gateway errors. We will post more information as it becomes available.

2. monitoring Aug 24, 2026, 09:23 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 24, 2026, 10:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 20, 2026, 03:19 PM UTC· resolved Aug 20, 2026, 09:24 PM UTC

1. identified Aug 20, 2026, 03:19 PM UTC

   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.

2. resolved Aug 20, 2026, 09:24 PM UTC

   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.

Read the full incident report →

Started Aug 19, 2026, 05:12 PM UTC· resolved Aug 19, 2026, 05:41 PM UTC

1. investigating Aug 19, 2026, 05:12 PM UTC

   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.

2. monitoring Aug 19, 2026, 05:26 PM UTC

   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.

3. resolved Aug 19, 2026, 05:41 PM UTC

   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.

Read the full incident report →

Started Aug 18, 2026, 04:03 PM UTC· resolved Aug 20, 2026, 02:51 PM UTC

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.

Read the full incident report →

Started Aug 07, 2026, 06:30 PM UTC· resolved Aug 07, 2026, 06:30 PM UTC

1. resolved Aug 07, 2026, 07:27 PM UTC

   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.

Read the full incident report →

Started Jul 24, 2026, 10:05 PM UTC· resolved Jul 31, 2026, 09:38 PM UTC

1. investigating Jul 24, 2026, 10:05 PM UTC

   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.

2. monitoring Jul 30, 2026, 10:41 PM UTC

   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.

3. resolved Jul 31, 2026, 09:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 26, 2026, 02:47 PM UTC· resolved Aug 05, 2026, 04:32 PM UTC

1. investigating Jun 26, 2026, 02:47 PM UTC

   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.

2. resolved Aug 05, 2026, 04:32 PM UTC

   The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.

Read the full incident report →

Started Jun 16, 2026, 07:20 PM UTC· resolved Jun 24, 2026, 09:47 PM UTC

1. investigating Jun 16, 2026, 07:20 PM UTC

   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.

2. resolved Jun 24, 2026, 09:47 PM UTC

   The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.

Read the full incident report →

Started May 21, 2026, 05:30 AM UTC· resolved May 21, 2026, 05:30 AM UTC

1. resolved May 21, 2026, 07:07 PM UTC

   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.

Read the full incident report →

Started May 20, 2026, 03:41 PM UTC· resolved May 20, 2026, 07:30 PM UTC

1. investigating May 20, 2026, 03:41 PM UTC

   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.

2. investigating May 20, 2026, 03:43 PM UTC

   We are continuing to investigate this issue.

3. resolved May 20, 2026, 04:36 PM UTC

   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.

4. postmortem May 20, 2026, 06:29 PM UTC

   **Update:** We previously marked this incident as resolved, but we have since identified additional accounts that may be affected. Our team is actively investigating and working to restore access. We apologize for the confusion and will continue to provide updates here as we learn more. As a reminder, responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.

Read the full incident report →

Started Apr 22, 2026, 04:00 AM UTC· resolved Apr 22, 2026, 04:00 AM UTC

1. resolved Jun 10, 2026, 05:52 PM UTC

   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.

Read the full incident report →

Started Apr 17, 2026, 04:30 AM UTC· resolved Apr 17, 2026, 04:30 AM UTC

1. resolved Apr 17, 2026, 02:09 PM UTC

   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.

Read the full incident report →

Started Apr 07, 2026, 07:35 PM UTC· resolved Apr 08, 2026, 02:49 PM UTC

1. investigating Apr 07, 2026, 07:35 PM UTC

   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.

2. monitoring Apr 07, 2026, 11:56 PM UTC

   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.

3. resolved Apr 08, 2026, 02:49 PM UTC

   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.

Read the full incident report →

Started Mar 26, 2026, 02:50 PM UTC· resolved Mar 26, 2026, 03:57 PM UTC

1. investigating Mar 26, 2026, 02:50 PM UTC

   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.

2. monitoring Mar 26, 2026, 03:18 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 26, 2026, 03:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 12, 2026, 07:10 PM UTC· resolved Feb 12, 2026, 08:22 PM UTC

1. investigating Feb 12, 2026, 07:10 PM UTC

   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.

2. monitoring Feb 12, 2026, 07:55 PM UTC

   A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.

3. resolved Feb 12, 2026, 08:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 02, 2026, 08:27 PM UTC· resolved Feb 04, 2026, 08:27 PM UTC

1. investigating Feb 02, 2026, 08:27 PM UTC

   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.

2. identified Feb 02, 2026, 08:58 PM UTC

   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.

3. resolved Feb 04, 2026, 08:27 PM UTC

   The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.

Read the full incident report →

Started Jan 29, 2026, 02:51 PM UTC· resolved Jan 29, 2026, 02:51 PM UTC

1. resolved Jan 29, 2026, 02:51 PM UTC

   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.

Read the full incident report →