We have released a new version to resolve this issue. If you are on R12.11.18 and receive have tables with With Japanese or Special Characters, please work with you CS team to schedule an ad hoc upgrade. Otherwise, you will be upgraded during your regular scheduled upgrade window.
Posted Dec 18, 2025 - 00:18 UTC
Identified
We have identified the issue and we are working on a fix. If you encounter this issue or need assistance restoring workspace access, please submit a ticket to Support and our team will assist promptly.
Posted Dec 15, 2025 - 22:58 UTC
Investigating
Impacted Version: R12.11.18 We are aware of an issue in version R12.11.18 where creating a table or report that includes Japanese or other special characters in the name may result in a server error. When this occurs, the associated workspace cannot be opened, and the changes cannot be reverted through the UI.
Our engineering team is actively working on a fix.
If you encounter this issue or need assistance restoring workspace access, please submit a ticket to Support and our team will assist promptly.
We will provide an update as soon as a fix is available.
Posted Dec 15, 2025 - 18:00 UTC
This incident affected: Europe (EU) - AWS (Costing, Billing, Demand, and TBM Studio), Australia (AU) - AWS (Costing, Billing, Demand, and TBM Studio), Middle East (ME) - AWS (Costing, Billing, Demand and TBM Studio), Japan (JP) - AWS (Costing, Billing, Demand and TBM Studio), Singapore (SG) - AWS (Costing, Billing, Demand and TBM Studio), and Americas (US2) - Azure (Costing, Billing, Demand and TBM Studio).