SMARTSHEET · Vendor
NO FIX YET · SEE WHAT TO DO
An upstream CRM provider outage caused intermittent errors in Smartsheet's Salesforce Connector and Customer Support Portal case creation on September 16, 2026. Some connectors that refreshed credentials during the outage may have kept an expired authentication token; this is an availability incident, not an attack.
first public Sep 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Customers who use the Smartsheet Salesforce Connector or the Customer Support Portal to create cases during the September 16, 2026 outage window. Customers whose connectors were refreshing credentials during that window may have an expired token and need to reconnect. Customers without the Salesforce Connector are not affected.
Not affected if no-salesforce-connector
Who cares saas, salesforce, security, smartsheet
On September 16th, 2026, starting at approximately 3:36 AM PDT, customers began experiencing intermittent errors with the Salesforce Connector and with creating cases through the Customer Support Portal. The issue was caused by a widespread outage at our upstream CRM service provider, which affected instance stability and API availability across multiple regions.
Our team began monitoring the provider's status closely once impact was confirmed and worked in parallel with them as they rolled out a fix fleetwide. The rollout proceeded in stages and needed to be reapplied to a subset of instances before it fully took hold, which is why customers continued to see intermittent errors throughout the morning even as conditions improved. By 11:51 AM PDT we were observing sustained stability, and our upstream provider confirmed full resolution on their end at approximately 11:59 AM PDT. We confirmed the Salesforce Connector and Customer Support Portal were fully restored and operating normally by 2:02 PM PDT.
Some customers who had connectors actively refreshing credentials during the outage window may have been left with an expired authentication token as a residual effect, since our provider's authentication endpoint was also impacted. Affected customers can resolve this by reconnecting the Salesforce Connector to obtain a fresh token and re-enabling any workflows that were disabled as a result.
This page as .md ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.