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.
identified
The issue has been identified and a fix is being implemented.
monitoring
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.
resolved
This incident has been resolved.
postmortem
**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.
Investigating assets unexpectedly moved from Folders to the Parent Workspace
์์ 2026๋ 6์ 3์ผ PM 8:28 UTC ยท 2d 3h
Pending
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
ReportsSheetsDashboards
investigating
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.
identified
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.
identified
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
investigating
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
monitoring
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.
resolved
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.
postmortem
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.
Sheets Not Loading/Opening โ "Trouble Reaching Smartsheet" Error
์์ 2026๋ 5์ 27์ผ PM 5:50 UTC ยท 7h 1m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Sheets
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
monitoring
We are continuing to monitor for any further issues.
resolved
This incident has been resolved.
postmortem
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.
Investigating Workspace panel not opening or closing unexpectedly
์์ 2026๋ 4์ 22์ผ PM 4:45 UTC ยท 2h 34m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Search
investigating
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.
identified
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.
monitoring
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.
resolved
Workspace panel functionality has been fully restored and is operating normally. The incident is now resolved.
postmortem
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Failures during Form Submissions
์์ 2026๋ 4์ 13์ผ PM 4:33 UTC ยท 4h 13m
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Forms
investigating
We are currently investigating an issue affecting Smartsheet Forms where a subset of users are experiencing failures when submitting forms.
investigating
We are continuing to investigate this issue.
monitoring
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.
resolved
Forms Submissions are operating normally. The incident is now resolved.
postmortem
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.
Proof Performance and Watermarks
์์ 2026๋ 3์ 31์ผ PM 6:53 UTC ยท 3h 8m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Document Proofing
investigating
We are currently investigating an issue causing 'EVALUATION MODE' watermarks and slow loading on proofs. We will provide an update in 30 minutes.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
User & Group Management
์์ 2026๋ 3์ 24์ผ PM 3:16 UTC ยท 3h 13m
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
User and Group Management
investigating
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.
identified
The issue has been identified and a fix is being implemented.
monitoring
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.
resolved
This incident has been resolved.
postmortem
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.
Form Submissions issue
์์ 2026๋ 3์ 3์ผ PM 5:16 UTC ยท 1d 6h
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Forms
investigating
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.
identified
The issue has been identified and a fix is being implemented.
identified
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
Forms Submissions has been fully restored and is operating normally. The incident is now resolved.
postmortem
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.
Brandfolder Monthly Reports Delayed
์์ 2026๋ 2์ 27์ผ PM 9:55 UTC ยท 24d 20h
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Insights
identified
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.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on restoring full service.
identified
A fix is being implemented. An update will be shared once completed.
identified
We are finalizing the fix for this issue and will have an update shortly.
monitoring
We have implemented the fix fully and we are monitoring for stability.
resolved
This incident has been resolved.
postmortem
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.
PROD-AU home not loading
์์ 2026๋ 2์ 22์ผ PM 12:17 UTC ยท 2h 28m
Outage์ฌ๊ฐํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
ReportsDynamic ViewSheetsDashboards
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
Resource Management Advanced reports failing to create and refresh.
์์ 2026๋ 2์ 17์ผ PM 4:08 UTC ยท 2h 47m
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Resource Management
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.