# Salesforce: Tableau Feature Disruption: Analytics Cloud

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-04-01 17:00 UTC · Resolved: 2026-04-02 07:53 UTC · Duration: 15 h
- Updates: 5 · Affected components: Analytics Cloud, 7 instances
- [Vendor status page: https://status.salesforce.com/incidents/20003897](https://status.salesforce.com/incidents/20003897)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-04-02 02:40 UTC: At 00:53 UTC on April 2, 2026, we became aware of an issue impacting Tableau Cloud customers attempting to run Prep Flows. A subset of customers may experience failures when initiating these flows. This is primarily happening in our Japan region, but there is some minimal occurrence in other regions as well. We’re actively engaged and are exploring multiple paths to resolution. We will provide an update as additional information is available.
- **update** 2026-04-02 02:57 UTC: Upon further investigation, we have determined that the start time of impact is different than initially understood. We have now revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- **update** 2026-04-02 05:38 UTC: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- **update** 2026-04-02 08:22 UTC: We’ve resolved the issue for all affected customers. The problem was caused by an issue in the background processing pods, where certain processes stopped before flows could start. We resolved this by refreshing the affected pods. We apologize for any disruption this may have caused. A full investigation is underway to determine the root cause and prevent similar issues in the future.
- **update** 2026-04-03 14:59 UTC: We have determined that the EW1A pod was not impacted during the times outlined and will now be removed from this post. We apologize for any inconvenience caused by the false positive notification, and we will undertake a full investigation as we work to improve our impact alerting and assessment configurations


---
Canonical: https://rewindex.com/company/salesforce/incidents/20003897 · Markdown: https://rewindex.com/company/salesforce/incidents/20003897.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003897 · Generated 2026-10-18T11:26:21.374Z