58 Smartsheet incidents · 2025年1月 — official updates, affected components, duration and resolution details.
我们正在调查一个故障 撞击登录, 工作表访问,控制中心和动态视图。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个问题, 美国Smartsheet案例的一些工作单没有加载。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
我们仍在调查一个问题 美国Smartsheet中的一些工作单 未能加载。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
我们仍在调查一个问题 美国Smartsheet中的一些工作单 未能加载。 这个问题也影响到报告和Dashboards以及Premium Apps,包括动态视图、工作apps和资源管理。 我们的小组仍然充分参与处理这一局势。 我们将继续经常提供最新情况,直到我们达到监测状态.
我们正在继续调查这一问题.
我们已实施了一个缓解问题的措施, 导致美国Smartsheet实例中的纸片无法加载, 系统衡量标准目前正在显示恢复,我们的小组正在积极监测这项服务,以确保充分稳定。 我们将发布进一步的最新消息,直到事件完全解决.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查影响细胞链接和交叉工作表参考资料的延误或失败。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
我们仍在调查这一问题。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
这一问题已经确定,目前正在解决.
一项固定措施已经执行,我们正在监测这项服务,以确保稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在用工作单、报告和工作流程来调查问题。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
我们正在继续研究这个问题,并努力争取尽快实现缓解.
缓解措施已经到位,我们看到强劲复苏。 我们将继续密切监测,以证实这个问题已经完全解决.
这一事件已经得到解决.
8月11日大约从7:00到4:20 PM PDT,一些客户在加载工作单和报告时遇到超时或故障,以及自动化工作流程出故障,由于出错率高导致一些工作流程被禁用. 这一事件是由与最近服务中断背后的条件有关的数据库查询路线问题所引发的,其中某些读取内容被路由到主写服务器,一个涉及工作表同步的边缘案例放大了由此产生的负载. 我们把服务稳定在3:20 PM PDT, 并证实PM PDT4:20完全恢复, 我们确定并部署了一个永久的代码固定,以纠正查询路径. 我们还正在改进监测和保障措施,以及早发现并减轻类似情况.
自动翻译自官方事件更新。
我们正在调查Smartsheet、撞击平面、溢价应用程序、连接器和API中缓慢和超时的错误。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
我们确定了Smartsheet缓慢和超时问题的责任问题,并正在执行一个解决办法。 我们将经常提供最新情况,直到我们达到监测状态.
我们正在观察Smartsheet、Premium Apps、连接器和API的稳定性恢复。 我们正在继续密切监测,以确认全面服务稳定。 一旦决议得到确认,我们将提供最新情况.
我们正在继续监测任何其他问题.
这一事件已经得到解决.
2026年7月30日,在协调世界时约11:00至15:57之间,一些客户无法加载床单并经历API超时. 这还影响到控制中心、表格视图、时间线和董事会视图、报告、Dashboards、Formats、动态视图和Bridge集成。 原因是后端服务,在上午的交通暴动中受到重载CPU. 其自动健康检查开始清除超载病例的速度快于替换人员能够上线的速度,服务的最低容量设置太低,无法吸收损失. 我们的工程师解决了这个问题,提高了服务的能力限度,恢复了健康的能力,并在几分钟内使性能恢复正常. 没有丢失数据 。 我们永久地提高了能力,我们正在调整健康检查,增加早期的基础设施一级监测,并建立一个预防类似问题并加快恢复速度的运行本.
自动翻译自官方事件更新。
我们正在调查一个问题 防止Smartsheet美国成功加载。 尝试登录到 Smartsheet US 或访问项目可能导致加载屏幕不完成 。 我们将在30分钟后提供最新情况.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
从2026年7月15日大约1:44AM PT起,一些客户可能在执行依赖于Smartsheet授权检查的行动时出错,例如资产访问检查. 这是由于在例行系统更新期间出现一个临时问题,这短短地导致一部分请求被转到我们基础设施中无法使用的部分。 在此期间,受影响的请求可能已经失败. 问题被确定并纠正,恢复正常运行.
自动翻译自官方事件更新。
我们正在通过自动工作流程和人工触发程序,调查关于缺少或延迟更新/核准请求通知和电子邮件的报告。 我们的团队充分参与处理这一局势。 我们将经常提供最新情况,直到我们达到监测状态.
造成更新/核准请求通知和电子邮件缺失或被延迟的问题已经查明。 我们的团队正在执行一个解决方案。 我们将经常提供最新情况,直到我们达到监测状态.
为了解决缺少或延迟更新/核准请求通知和电子邮件的问题,已经实施了一个固定办法,我们正在监测结果.
这一事件已经得到解决.
2026年6月24日,一个自动化的工作流程在短时间内产生了异常多的更新请求,这暂时打乱了负责发送通知邮件和应用程序内提示的内部事件处理基础设施. 这导致约85%的更新请求和批准请求通知被延迟了约13小时。 没有丢失数据,一旦系统恢复,所有通知最终都会发出。 自那时以来,我们实施了自动化回收机制,并正在增加保障措施,以防止今后过多的请求会影响通知程序.
自动翻译自官方事件更新。
我们知道,一些客户正在通过公开Smartsheet表格收到更多的不想要的垃圾邮件,即使启用了reCAPTCHA。 我们的小组一直在积极调查和部署更多的保护。 随着我们继续应用和评价进一步的缓解措施,我们看到垃圾邮件活动减少。 受影响者: 使用不需要登录的公共表格的客户.
我们已采取措施,用Smartsheet公共表格解决垃圾邮件活动增加的问题。 我们将继续进行监测,并视需要作进一步调整。 如果你继续看到大量垃圾邮件提交,请与我们的支助小组联系,以便我们进一步调查.
现在解决了这个问题。 我们仍然在积极监测垃圾邮件数量,作为一项持续和不断发展的战略。 我们鼓励所有顾客 提交支持票 任何剩余垃圾邮件通过 这样我们就可以继续 微调我们的解决方案.
从5月下旬开始,我们看到向公共Smartsheet表格\(提供给公众的表格,不需要Smartsheet登录\)提交的垃圾邮件数量和复杂程度明显增加,即使启用了Captcha设置。 这导致一些客户的不想要的垃圾邮件含量增加,这些垃圾邮件往往含有密码货币或钓鱼链接,并寄入其单子。 这项活动是由通过匿名网络和代理服务运作的自动bots产生的。 这主要影响到但不限于美国地区。 一旦查明虐待情况,我们就在接下来的几周里对一系列保护措施进行评估、部署、测试和调整。 由于这种自动滥用随着时间推移而适应,因此要解决这个问题需要一种迭接方式:我们分层以两种形式保护多种保护,即captcha服务,以及基础基础设施,评估它们相对于活体交通的效果,并在我们学到更多东西时加以改进,调整或取代被证明不太有效的措施。 在这一过程中,我们还监测并努力纠正在此期间可能发生的对合法形式提交的任何意外影响。 自动垃圾邮件现在被大量阻塞到几乎为零的速度,对合法提交文件的影响很小或没有影响。 我们还积极将类似的保护带入Smartsheet政府环境。 从7月8日的1:46PT开始,我们标出这个问题已经解决了. 如果您仍在观察垃圾邮件提交, 请首先确保您在表格上启用 Captcha 。 如果 Captcha 已启用, 您仍然看到垃圾邮件, 请在表格上使用“ 报告滥用” 链接提交报告 。 我们总是建议应用符合您解决方案的[最高格式安全限制](https://help.smartsheet.com/articles/2481836-manage-form-display-and-supplement-options#toc-security),并在必要时强制执行[admin Center](https://help.smartshe.com/articles/2483290-apply-security-set-s-forms-forms). 我们将继续监测、调整和加强这些保护。 这包括让 Captcha 默认启用所有新表格的更改和向系统管理员推出的新行政控制,使其有能力强制Captcha 对其计划管理的表格。 我们知道我们的服务对我们的客户有多重要 并且为这起事件对你和你的生意的影响道歉 我们承诺,我们将尽一切可能从这一活动中吸取教训,并利用这一经验推动改善我们的服务,以确保Smartsheet成为可以指望交付的伙伴。 我们知道,你的成功——以及你对Smartsheet的持续信任——取决于这一点.
自动翻译自官方事件更新。
We are investigating the Smartsheet add-ons for Google which is currently not available. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
The issue has been identified and a fix is being implemented.
The Smartsheet and Brandfolder add-ons for Google Docs, Sheets, and Slides were unavailable due to a Google platform change that required all affected add-ons to be redeployed. Our team has applied the necessary fixes and we are currently monitoring to confirm full stability.
This incident has been resolved.
**The Smartsheet Merge add-on for Google Docs stopped working after Google removed support for an older runtime environment that the add-on depended on, causing the add-on to fail entirely for all users \(~234,000 affected\).** The issue was resolved on June 11, 2026, by updating the add-on's code and deployment configuration to be compatible with Google's current platform — no customer data was lost.
We are investigating an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
We have identified the issue responsible for the assets unexpectedly moved from Folders to the Parent Workspace and implemented a fix. We will provide frequent updates until we reach a monitoring status.
We are continuing our investigation into an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status. Components: Core App - Sheets, Reports, Dashboards - Degraded
We are continuing our investigation into an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users, and we are diligently working to restore them to their original location. We will provide frequent updates until we reach a monitoring status.
We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work diligently to restore them to their original location. We will provide frequent updates until we reach a monitoring status.
We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work diligently to restore them to their original location. We will provide updates until we reach a monitoring status.
We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work on restoring assets to their original location, and some customers should begin to see assets restored to their original locations. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.
We identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Assets that were moved to the Parent Workspace as a result of this issue cannot be moved by users. We are continuing to restore assets to their original location, and some customers should begin to see assets in the correct folder structure. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.
We identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Assets that were moved to the Parent Workspace as a result of this issue cannot be moved by users. We have restored some assets to their original locations, and some customers should begin to see assets in the correct folder structure. We are continuing to restore assets to their previous locations. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.
We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users will be unable to move affected assets until we restore them to their original locations. We have processed some of the affected assets, and some customers will see they have been restored to their prior locations. We continue to work on restoring assets to their original locations, and we will provide updates until we reach a monitoring status.
We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users cannot move affected assets until they are restored to their original locations. We have processed some of the affected assets, and some customers will see they have been restored to their prior locations. We are continuing to work on restoring assets to their original locations, and we will provide updates until we reach a monitoring status.
We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users cannot move affected assets until they are restored to their original locations. We have processed the majority of affected assets, and the customers will see they have been restored to their prior locations. We are continuing to work on restoring the remaining assets to their original locations, and we will provide updates until we reach a monitoring status.
We've identified and fixed the root cause of assets moving from Folders to the Parent Workspace. Our restoration process is complete and we have confirmed 99.98% of the affected assets have been returned to their correct locations. If you find any misplaced assets, you have two options: 1. Move them manually – items can be repositioned directly within the platform. 2. Open a support ticket – if you encounter errors or high volume, reply to an existing ticket or open a new one to engage our support team When contacting support, please include: • Workspace ID • Sheet ID(s) of affected assets • Reference: INC-1089 We apologize for the disruption and appreciate your patience.
We've identified and fixed the root cause of assets moving from Folders to the Parent Workspace. Our restoration process is complete and we have confirmed 99.98% of the affected assets have been returned to their correct locations. If you find any misplaced assets, you have two options: 1. Move them manually – items can be repositioned directly within the platform. 2. Open a support ticket – if you encounter errors or high volume, reply to an existing ticket or open a new one to engage our support team When contacting support, please include: • Workspace ID • Sheet ID(s) of affected assets • Reference: INC-1089 We apologize for the disruption and appreciate your patience.
On Wednesday, June 3, beginning at approximately 11:15 AM PDT, a platform configuration change caused sheets, reports, dashboards, and folders to be unexpectedly moved from their original folder locations to the top level of the workspace. Affected assets could not be manually moved by users during this period. The issue was identified at 1:28 PM PDT and the root cause was isolated and remediated at 2:10 PM PDT, stopping any further impact. The issue affected customers across North America, European Union, and Australia regions. Our engineering team worked to identify and restore all affected assets back to their original folder structure. The restoration process was completed on June 5, at 12:53 PM PDT, with 99.98% of affected assets successfully returned to their correct locations. For any remaining items that may still appear out of place, they can safely be moved manually as needed. If you encounter issues when attempting to move items, need guidance, or if the volume is too large to address manually, please open a Support case at [https://supportportal.smartsheet.com](https://supportportal.smartsheet.com) referencing "INC-1089" and our team will assist with restoration directly. We sincerely apologize for the disruption this caused. We are making improvements based on our learnings from this incident to prevent similar issues in the future.
We are currently investigating reports of sheets failing to open and displaying the error "We're having trouble reaching Smartsheet right now." Our team is actively working to resolve the issue and will provide frequent updates until we reach a monitoring status.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
On May 27, 2026, from approximately 8:30 AM to 2:00 PM PDT, some customers were unable to load sheets, receiving the error, "We're having trouble reaching Smartsheet right now." This was caused by an unexpectedly high volume of simultaneous database requests triggered when loading configuration data for sheets with forms containing numerous column options. Under elevated traffic, this pattern generated hundreds of parallel queries, overwhelming the affected database cluster's read capacity. We resolved the issue by scaling database read capacity and routing traffic away from the affected infrastructure. To prevent recurrence, we are implementing changes to: * Redesign how column option data is fetched to reduce load. * Better distributing database traffic and protecting database capacity during periods of high usage. * Improving monitoring and tooling to detect and respond to issues faster. We know how critical our services are to our customers and apologize for any impact this incident may have had on you and your business. We promise that we will do everything we can to learn from this event and use it to drive improvement across our services to ensure that Smartsheet is a partner that can be counted on to deliver. We know that your success—and your continued trust in Smartsheet—depends on it.
We are investigating reports of the Workspace panel not opening or closing unexpectedly. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
We have identified the issue responsible for the Workspace panel not opening or closing unexpectedly and are implementing a fix. We will provide frequent updates until we reach a monitoring status.
We are observing stability being restored for Workspace panel not opening or closing unexpectedly. We are continuing to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.
Workspace panel functionality has been fully restored and is operating normally. The incident is now resolved.
Between 22:40 UTC on April 21 and 19:21 UTC on April 22, the Workspace Panel was not rendering consistently for users. Regardless of whether they had toggled it on or off, the panel did not appear. The issue was particularly present for non-Enterprise users \(Business and Pro accounts\). The impact was limited to the panel and did not affect any other UI flows within the Smartsheet app. The incident was resolved by rolling back the affected Workspace Panel to a previous known good version.
We are currently experiencing intermittent loading issues with the Resource Management module within Smartsheet. Please note that the standalone site at rm.smartsheet.com is working normally and can be used as a workaround while we resolve the integration issues.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue affecting Smartsheet Forms where a subset of users are experiencing failures when submitting forms.
We are continuing to investigate this issue.
The issue has been identified, Form submissions are operating normally now. Our team will continue to monitor the service and implement the necessary changes to prevent recurrence.
Forms Submissions are operating normally. The incident is now resolved.
On Monday, April 13, between 7:00 AM and 11:30 AM PST, some users experienced failures when submitting Smartsheet forms. The issue was isolated to CAPTCHA-enabled forms and was caused by a problem with our reCAPTCHA verification endpoint. Error rates declined significantly by mid-morning and the incident was fully resolved by 11:30 AM PST. All form submissions are operating normally.
We are currently investigating an issue causing 'EVALUATION MODE' watermarks and slow loading on proofs. We will provide an update in 30 minutes.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On March 30, 2026, at approximately 10:55 PM PDT, the Proofing service encountered issue where users encountered watermarks on all legacy proofs. The outage was caused by a licensing issue and was also compounded by an internal configuration issue causing a full proofing outage. The incident was mitigated by March 31, 2026 at 1:15PM PDT To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for licensing issues as well bolstering deployment stability.
We are investigating blank results showing on User & Group Management pages in Admin Center. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
The issue has been identified and a fix is being implemented.
We are observing stability being restored for the User & Group Management pages in Admin Center. A page refresh or clearing of cache from this page from your browser might be necessary for full resolution. We are continuing to monitor it closely to confirm full service stability.
This incident has been resolved.
On March 24, 2026, at approximately 07:55 UTC, the Admin Center Client experienced an issue where users were unable to view user groups in the Group Management view and users in the User Management page in certain cases — instead seeing an infinite loading screen. The issue was caused by a recent update to a shared part of the Admin Center interface that controls how loading indicators are shown during searching. In the Group Management area and UserView, this change accidentally made the page think it was always still loading, so users saw a never-ending loading screen and couldn't view groups \(and in some cases users\). The problem was fixed by rolling back that change, which finalized at 09:06 UTC. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for failed page renders in key Admin Center views, adding automated synthetic tests, and documenting recovery runbooks to reduce future resolution time.
We've investigating an issue with Form Submissions propagating to the sheet. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
The issue has been identified and a fix is being implemented.
This issue has been identified and a fix has been implemented for new form submissions. For previous form submissions that failed in this window, a manual replay will be ran. Please do not re-submit these form submissions.
A fix has been implemented and we are monitoring the results.
Forms Submissions has been fully restored and is operating normally. The incident is now resolved.
On 4:47PM Pacific Standard Time, March 2nd, 2026, a code regression impacted a subset of Form Submissions to propagate to the underlying sheets and some API requests. Service was restored by rolling back to the last known stable deployment. A manual scale up was applied to meet the demands of the queues. Issue was successfully resolved by 9:53AM PST March 3rd, 2026. All previously failed form submissions were successfully replayed by 12:20PM PST, March 4th, 2026.
We have proactively paused the release of our February reports to ensure the highest level of data accuracy. Our team is currently resolving a synchronization issue, and we expect the corrected reports to be available shortly. We apologize for the inconvenience and appreciate your patience while we ensure your data is 100% correct.
We are continuing to work on a fix for this issue.
We are continuing to work on restoring full service.
A fix is being implemented. An update will be shared once completed.
We are finalizing the fix for this issue and will have an update shortly.
We have implemented the fix fully and we are monitoring for stability.
This incident has been resolved.
On February 25, 2026, a data synchronization issue was identified in Brandfolder's reporting infrastructure. The logical replication pipeline between the production database and the analytics data layer fell out of sync, which caused stale or missing data in Insights dashboards, subscription page metrics, and the Insights Data Connector. Standard monthly reports were proactively paused on February 27 to prevent delivery of inaccurate data, and a partial outage was posted to the status page. Engineering began rebuilding the replication pipeline, but encountered multiple failures during the data catch-up process due to the volume of data \(~5TB\) and recurring initialization errors. The replication pipeline was stabilized on March 16 and data began flowing to the analytics layer. The team then identified and resolved gaps in session data for specific dates, re-ran the affected data pipeline jobs, and verified data parity between the production database and analytics systems. Standard reporting was resumed on March 24, 2026, and the incident was resolved the same day. All previously missed reports have been generated and delivered. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for the replication pipeline, adding automated data health checks, and documenting recovery runbooks to reduce future resolution time.
We are investigating the home page error message "Something went wrong". Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Approximately on 3:15AM Pacific Standard Time February 22nd, 2026 in our Australia region, a deployment was performed to resolve a performance issue. However, a configuration required to validate session cookies was incorrectly specified, which caused the web app to become inaccessible after successful login. The issue was mitigated within 80 minutes by toggling a feature flag to reroute traffic back to a stable service and full functionality was restored by 4:35AM Pacific Standard Time February 22nd, 2026.
We are investigating Advanced Reports not being able to create new ones and also failing to refresh. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On February 17th, 2026, a failure in the service linking Resource Management Workflows to the main Data Shuttle engine resulted in a service disruption for the Resource Management Advanced Reporting feature in the US Production environment. Service was restored by rolling back the most recent Data Shuttle deployment \(originally released five days prior\). While this action immediately resolved the issue, preliminary analysis indicates the root cause was likely a memory exhaustion issue within the service, rather than a defect in the deployment itself. The rollback effectively reset the service state, clearing the error. A comprehensive RCA is currently underway to pinpoint the source of the outage.