60 Formassembly incidents · 2024年3月 — official updates, affected components, duration and resolution details.
我们目前正在调查影响表格一级销售力量连接器的延迟处理报告,并在提交某些账户的表格后发出通知。 我们对此可能造成的任何不便表示歉意。 一旦获得更多信息,我们将提供最新资料.
影响到电子邮件通知和销售力量连接器的延迟处理已经得到解决。 受影响划界案在延误后得到成功处理。 我们已证实, 通知和连接器都正常处理.
自动翻译自官方事件更新。
我们目前正在调查关于缓慢和可能的网关出错的报告。 我们将公布更多信息.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
工作队已查明一个问题,即提交带有文件上传字段的表格会导致提交失败。 调查组目前正在研究这个问题.
决心 这个问题已经得到解决。 从8月18日1:03 PM ET到8月20日11:49 AM ET,由于托管架构改变期间引入了存储配置问题,政府云表提交文件所附带的文件没有被保存. 填好表格并保存答复;只有上载的文件受到影响。 此窗口上传的文件没有存储, 无法回收 。 这些报告需要再次提交。 其他所有响应数据都完好无损. 上传自8月20日11:49 AM ET开始正常运行,我们核实成功上传多个账户. 有具体答复问题的客户应联系表格大会支助.
自动翻译自官方事件更新。
我们正在调查关于销售力量营销云(SFMC)预填和提交连接器配置没有加载的报告. 使用 SFMC 预填连接器的表格目前可能无法访问 。 我们的团队正在积极调查这个事业,我们将很快分享最新消息.
我们找出了影响销售力量营销云(SFMC)预填和提交连接器的问题原因,并应用了固定. 连接器的配置现在应该正常地加载,受影响的表格应该可以再次取用。 我们正在密切监视 以证实完全恢复.
这一事件已经得到解决。 我们查明并纠正了根本问题,销售力量营销云(SFMC)预填和提交连接器目前正在按预期装入和运行。 受影响的形式又可以使用。 请注意,在2026年8月19日9:20 AM至1:20 PM ET之间提交的一组回复可能并未被发送至销售力量营销云,可能需要手动再处理. 我们建议审查在这一窗口和后处理期间提交的答复,任何未按预期同步的答复。 谢谢你的耐心.
自动翻译自官方事件更新。
我们正在调查关于表格一级的销售力量连接器和表格通知没有在提交表格时处理子账户的报告。 我们正在积极调查,并将在获得更多信息后提供最新情况.
我们正在继续调查这个问题。
我们缓解了影响销售力量连接器提交和通知的处理延误。 处理工作已恢复正常,受影响划界案和通知现在应如预期的那样进行。 说明: 这是处理延迟,不是失败。 受影响的提交材料和通知已排队,应自动完成,而无需重新处理。 可能的重复记录: 如果在提交材料被延迟时手动重新处理,你可以看到一份在 Salesforce 中的重复记录——一份来自原始提交材料,一份来自后处理尝试。 我们建议审查最近重新处理的重复提交材料.
虽然我们希望昨天的反应是彻底的,但顾客继续遇到不定期的拖延问题。 该小组已查明潜在原因,并正在积极进行这项工作。 有了新的资料,我们将继续在此张贴.
这一事件已经得到解决。 如果你继续遇到麻烦,请伸出援手.
自动翻译自官方事件更新。
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.
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.
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.
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.
我们目前正在调查涉及某些账户的破坏或无效销售力授权的报告。 遵循以下步骤恢复连接 : 在重新授权之前, 请检查您目前在 Salesforce 中有多少活动连接 。 单击位于 Salesforce 右上角的配置图标,然后进入设置 > 管理连接。 - 在OAuth Apps表格中,请检查FormAssembly Connector出现多少次. 销售力允许每个连接的应用程序最多有5个连接. - 如果您已经拥有了五个FormAssembly Connector连接,请取消与最小使用数的连接。 这将释放出一个符号,并有助于防止销售力公司取消仍在积极使用的连接。 接下来,返回FormAssembly。 在右上角浏览您的用户名并选择外部授权 。 重新授权标记为无效的任何连接 。 - 如果连接不到5个,请在FormAssembly右上角的用户名上徘徊,并选择外部授权。 然后,重新授权任何标记为无效的连接 。 如果你继续遇到问题 请联系我们的支援小组.
以及新报告数量大幅下降。 我们正继续密切监测局势.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.
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.
The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.
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.
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.
We are continuing to investigate this issue.
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.
**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.
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.
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.
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.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.
This incident has been resolved.
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.
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.
The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.
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.
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.
This incident has been resolved. Please reach out to [email protected] if you run into any further issues.