Ironclad 中断历史

1. 2026年10月21日 UTC 15:05monitoring

   目前正在发生影响 Dropbox 标志的事件。 我们将随时提供最新情况.

2. 2026年10月21日 UTC 16:30resolved

   The incident with Dropbox Sign has been resolved.

自动翻译自官方事件更新。

1. 2026年9月4日 UTC 04:20investigating

   拥有首选语言设置的用户,当用户将首选语言切换到除英语(美国)之外的其他任何语言时,会造成空闲和长时间的负载. 我们的小组正在努力执行解决这个问题的固定办法.

2. 2026年9月4日 UTC 05:25resolved

   我们已经解决这个问题.

自动翻译自官方事件更新。

1. 2026年8月28日 UTC 15:34investigating

   Ironclad目前与我们的电子邮件子处理器发生问题.

2. 2026年8月28日 UTC 16:53identified

   我们已查明与我们的一个电子邮件分处理器有关的问题,并正在努力执行一个固定办法.

3. 2026年8月28日 UTC 19:22resolved

   我们用我们的电子邮件分处理器解决了这个问题,你们现在应该看到寄来的电子邮件.

自动翻译自官方事件更新。

1. 2026年8月27日 UTC 21:06investigating

   我们与Mailgun找到了一个问题,它目前正在影响Ironclad平台。 在此期间,在Ironclad平台内发送或接收通知电子邮件、提醒电子邮件和签名电子邮件时可能出现出乎意料的延误或失败。 一旦这个问题得到解决,我们将立即提出报告.

2. 2026年8月27日 UTC 21:58monitoring

   我们已采取步骤处理电子邮件错误,并继续监测任何其他问题.

3. 2026年8月28日 UTC 01:52resolved

   我们处理了造成工作流程达到出错状态的问题,并正在积极努力解决受到影响的工作流程.

自动翻译自官方事件更新。

1. 2026年8月25日 UTC 13:53investigating

   Ironclad正在经历一个问题,居住在美国境外的客户可能会经历过长时间的耐久和长时间的负载. 我们正在积极调查这一问题并找出一项决议.

2. 2026年8月25日 UTC 15:39identified

   我们用我们偏好的语言设置确定了一个问题,当用户将其偏好的语言切换为英语以外的其他语言时,这个问题正在引起长时间和长时间的负载. 我们的小组正在努力执行解决这个问题的固定办法.

3. 2026年8月25日 UTC 16:49monitoring

   我们的团队已经部署一个固定器,所有用户现在都可以使用他们的首选语言设置,而无需经历空闲或长时间的负载.

4. 2026年8月25日 UTC 17:08resolved

   我们的团队已经部署一个固定器,所有用户现在都可以使用他们的首选语言设置,而无需经历空闲或长时间的负载.

自动翻译自官方事件更新。

1. 2026年8月20日 UTC 16:11investigating

   在Ironclad平台内采取行动时,用户可能经历略长的负载时间和一般的空闲时间. 我们的小组正在调查这一问题,我们认为,这个问题可能与我们的云基础设施提供者的中断有关,并正在努力确认其根源.

2. 2026年8月20日 UTC 18:01resolved

   这个问题已完全解决。 我们的小组确定,根源是云层基础设施供应商的中断,这造成了更长的载重时间和整个Ironclad平台的总体空隙。 性能已恢复正常;所有系统现已按预期运行。 感谢您在整个事件中的耐心,如果您继续遇到任何问题,请伸出援手.

自动翻译自官方事件更新。

1. 2026年8月18日 UTC 22:21investigating

   Ironclad是目前技术问题的经验。 我们知道,该平台无法进入,我们正在尽快解决这一问题.

2. 2026年8月18日 UTC 23:07resolved

   我们成功解决了这一事件. 我们完全恢复在线.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 22:10identified

   在推出我们新的全球条件特征时,Ironclad遇到了一个技术问题。 该团队迅速将特性去除,以安全地处理并重新启用该特性. 等全球条件重新启用后我们会在这里发布.

2. 2026年8月14日 UTC 01:02identified

   我们的团队仍在努力重新部署我们的全球条件特征。 完成后我们会更新状态页 所有系统全部上线.

3. 2026年8月14日 UTC 20:55resolved

   谢谢你的耐心 我们已经成功地推出了我们新的全球条件 在所有环境.

自动翻译自官方事件更新。

1. 2026年8月12日 UTC 13:59investigating

   We are actively investigating this issue an issue with Public Workflows. Currently if someone attempts to submit a Public Workflow they will receive a Form Validation Error.

2. 2026年8月12日 UTC 14:17resolved

   This issue has been resolved and all Public Workflows can be submitted as intended.

1. 2026年8月7日 UTC 18:09monitoring

   At the moment, Acrobat Services is experiencing technical difficulties which negatively impact's Ironclad's PDF -> DOCX conversion feature. We are monitoring their incident closely and will update our statuspage once Adobe's incident is resolved.

2. 2026年8月8日 UTC 00:54resolved

   Adobe has resolved their incident. Ironclad's PDF -> DOCX conversion services are fully restored.

1. 2026年8月5日 UTC 18:51investigating

   We are tracking a cross-customer performance issue with intermittent latency and loading failures across Production and Demo environments.

2. 2026年8月5日 UTC 21:24monitoring

   We continuing to investigate intermittent performance issues affecting some customers when using Ironclad. Our team is actively investigating the cause and working toward a resolution. We appreciate your patience and will provide another update as more information becomes available.

3. 2026年8月5日 UTC 22:09monitoring

   We are continuing to monitor and investigate the latency issues and will provide updates when available.

4. 2026年8月6日 UTC 17:02resolved

   We have resolved the intermittent latency and loading failures across all environments

1. 2026年7月29日 UTC 01:17investigating

   我们正在调查影响智能进口合同确认的更高出错率。 我们的团队确认这与上游的OpenAI事件有关 他们的团队已经承认了 智能导入请求处理已经部分恢复,但在验证服务稳定性的同时,合同类型提取仍然被禁用. 我们正在积极监测上游服务,一旦恢复全部功能,我们将发布另一份更新.

2. 2026年7月29日 UTC 01:21monitoring

   截至下午5时,OpenAI服务的提供情况有所改善,我们正在继续监测.

3. 2026年7月29日 UTC 02:38resolved

   OpenAI解决了影响智能进口合同承认的问题. 我们将继续监测,但所有受影响的功能都已恢复.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 23:19investigating

   对话搜索的性能正在下降。 我们正在继续调查.

2. 2026年7月21日 UTC 23:45resolved

   搜索正常运行 .

自动翻译自官方事件更新。

1. 2026年7月8日 UTC 17:30investigating

   We are actively investigating an issue affecting entity and counterparty search on workflow launch forms in production. Some customers may see “no matching options” when selecting an entity for their counterparty, which prevents certain workflows from being launched.

2. 2026年7月8日 UTC 19:43identified

   We've confirmed that the issue is tied to bad logic underlying how the Entity picker displays options to select. We are working on a fix to address this bad logic and making it available on Production as soon as we can.

3. 2026年7月8日 UTC 21:19monitoring

   We have implemented a fix for the issue affecting entity and counterparty search on workflow launch forms in production. We are seeing recovery and are continuing to monitor closely to confirm stable performance across impacted workflows.

4. 2026年7月8日 UTC 22:12resolved

   We have resolved the issue affecting entity and counterparty search on workflow launch forms in production. Customers will now be able to search for and select counterparties normally when launching impacted workflows. We will continue to review the incident internally.

1. 2026年7月1日 UTC 16:32investigating

   We are investigating an issue affecting Clickwrap. Impacted customers may see workflow processing failures or errors during submission. Our team is actively investigating and we will share another update as soon as we have more information.

2. 2026年7月1日 UTC 18:39monitoring

   We have implemented mitigation and are seeing recovery in Clickwrap. We are monitoring the platform closely while additional background services are brought back online. During the incident, impacted customers may have experienced workflow processing failures or errors during submission.

3. 2026年7月1日 UTC 19:07resolved

   The issue affecting Clickwrap has been mitigated and service has been restored. During the incident, impacted customers may have experienced workflow processing failures or errors during submission. We will continue to review the incident internally to confirm full stability.

1. 2026年6月24日 UTC 20:51investigating

   We are currently investigating an issue affecting the Ironclad Salesforce Managed Package where users may experience failures with document and approval syncing. This includes documents not syncing to and from Salesforce and approvals not reflecting correctly within the Ironclad Approval object. Our engineering team is actively working to identify the root cause. We will provide updates here as more information becomes available. Thank you for your patience.

2. 2026年6月24日 UTC 22:28identified

   We are currently investigating an issue affecting the Ironclad Salesforce Managed Package where users may experience failures with document and approval syncing. This includes documents not syncing to and from Salesforce and approvals not reflecting correctly within the Ironclad Approval object. Our engineering team is actively working to identify the root cause. We will provide updates here as more information becomes available. Thank you for your patience.

3. 2026年6月25日 UTC 01:09monitoring

   A code fix to address the syncing issue between Ironclad and Salesforce affecting documents and approvals has been deployed. We are actively monitoring that the fix is performing as expected.

4. 2026年6月25日 UTC 02:13resolved

   Our engineering team has confirmed that the code fix deployed to address the syncing issue between Ironclad and Salesforce is working as expected. Documents and approvals are now syncing successfully. This incident is resolved.

1. 2026年6月17日 UTC 16:30monitoring

   End users reported that they are unable to access records within Ironclad Repository. We identified the issue and implemented a fix and now all users can view records as intended.

2. 2026年6月17日 UTC 16:30resolved

   End users reported that they are unable to access records within Ironclad Repository. We identified the issue and implemented a fix and now all users can view records as intended.

1. 2026年6月4日 UTC 16:44resolved

   A fix has been implemented and the incident has been resolved. API requests are no longer receiving intermittent 502 error responses.

2. 2026年6月4日 UTC 16:44investigating

   API requests are experiencing intermittent 502 server error responses.

1. 2026年6月3日 UTC 19:45identified

   We are investigating an issue affecting some customers in **NA1 production** where **bulk** **document download, dashboard export, and preview actions are failing**. We have identified elevated errors in the document service and are actively working to mitigate the issue. Our current investigation indicates the problem is related to backend database latency impacting dependent document-processing jobs. We will share another update as soon as we have more information.

2. 2026年6月3日 UTC 19:57monitoring

   We've made changes on the backend to address the issues with downloads and exports and are monitoring for any further issues.

3. 2026年6月3日 UTC 20:10resolved

   We have verified and confirmed that the issue has been resolved

1. 2026年5月26日 UTC 18:49investigating

   Ironclad is currently experiencing Latency in platform. This may cause issues with updating workflows and records with users seeing an error ("Something is not working").

2. 2026年5月26日 UTC 22:06resolved

   We have resolved all latency issues in Production.