Known Issues

Issue Description A bug in the billing pipeline caused timeline generation to stall for multiple resource types. While raw state data continued to be collected, the final processing stage was interrupted, leading to gaps in billing timelines starting late April 2026. Affected Components Building Block billing timelines Tenant billing timelines Marketplace / Service Instance billing timelines Kubernetes resource billing timelines Impact Billing timelines may show gaps for the affected period. Usage reports for April and May may be incomplete for the resource types listed above. For tenant, marketplace, and Kubernetes resources , full reconstruction is possible provided the Processing Subscription retention time has not been shortened below the default of 65 days. If your organization has reduced this retention window, some data may not be fully recoverable. For Building Block timelines , full reconstruction is not possible. Data from **April 23 – May 1** is affected: recovery via backups is technically feasible but operationally intensive, and any data not explicitly recovered will remain unavailable until mid-May at the earliest. Workaround No workaround is available. Our team is actively regenerating usage reports for all affected customers back to April. Status and Next Steps The fix has been deployed with v2026.24.0 and usage report recalculation is in progress. A detailed impact statement will be communicated to affected customers. Contact Check in with our customer success team or support@meshcloud.io if you need any help.

When managing a Manual Building Block definition via the meshStack Terraform provider, including inputs of type SINGLE_SELECT or MULTI_SELECT causes a provider error: Provider produced inconsistent result after apply .version_spec.outputs: new element "my_input" has appeared. Root cause: The Manual implementation type automatically mirrors all inputs to outputs during a run. For non-basic input types ( SINGLE_SELECT , MULTI_SELECT ), meshStack maps these to STRING or CODE outputs respectively. The Terraform provider does not account for this auto-generated output and reports it as an unexpected state change. Workaround: Define only STRING , INTEGER , BOOLEAN , or CODE inputs in Manual Building Block definitions managed via Terraform. SINGLE_SELECT and MULTI_SELECT inputs can be used when managing the building block definition through the meshStack UI. Affects: meshStack Terraform provider users managing Manual Building Block definitions that include SINGLE_SELECT or MULTI_SELECT input types. The underlying meshStack runtime fix (auto-mapping input types to valid output types) was shipped in v2026.19.0. A provider-side fix to handle the auto-generated outputs gracefully is in progress.

In some cases, the meshPanel displays outdated state after navigating between views without a full page reload. Two known symptoms: False "no payment method assigned" warning — The panel keeps showing a payment method warning even though a payment method has already been assigned. False "You are not a member of this project" error — After navigating to a project the user is a member of, a membership error is incorrectly displayed. Workaround: Performing a full page reload resolves the issue in both cases. We are tracking this as a state management improvement to ensure the UI correctly refreshes its state after navigation, without requiring a manual reload.

I created a new draft version for a parent Building Block Definition and added a new output to it. When I go to the child and it is also a draft, I would expect to be able to pick this new output, as I want to develop both definitions in parallel as the new child version relies on the new parent output. But I only see the outputs of the released version. The workaround to this issue is, to first release the new version of the parent definition, which should be a feasible approach in most cases. But it would improve the experience for a Building Block Definition developer, if he could first test both definitions with the new dependency in its own workspace before releasing them in the new version. If the parent definition is draft in v1, it just works fine and I can pick all outputs. But when it was already released before and I just create a new draft version of it, it does not work as I expected it to work.

Detailed tenant usage reports, which are available for OpenShift, OpenStack, Cloud Foundry, and OSB Services, provide additional insights into usage data. However, even when currency conversion is enabled, these reports continue to display the original currency from the provider instead of the converted currency. Thanks for your understanding while we are working to solve this issue

We recently had the case that our Entra deleted users by accident and this triggered the deactivation of users in meshStack. Entra team created new users, the new users got new object ids. After 30 days, Entra sent a delete command to meshStack for the users with the old object ids. This triggered a deletion of users in meshStack. Expected: meshStack SCIM sync differentiates users by object id, not by username.

Description: When a user is assigned multiple roles within the same workspace (e.g., both Workspace Owner and Workspace Manager), they receive duplicate email notifications related to communications, role expiration, and similar events. This occurs because the system treats each role independently for notification purposes. Impact: Affected users may experience confusion or cluttered inboxes due to receiving multiple copies of the same email notification. Workaround: To avoid duplicate notifications, assign only the highest applicable role to the user within the workspace.

Description: When a tenant (e.g., a GCP project) incurs no cost—either due to inactivity or because all usage is covered by free consumption credits—the tenant is no longer displayed in the Unmanaged Tenant List. Additionally, Tenant Usage Reports are not generated or shown in such cases. Impact: This behavior reduces transparency, as it prevents users from tracking resource consumption even when costs are offset by credits. As a result, tenants utilizing free credits may appear inactive or unaccounted for in reporting and monitoring views. Expected Behavior: Even if no charges are incurred, tenants should remain visible in the Unmanaged Tenant List and Tenant Usage Reports should reflect credit-based consumption. This would ensure full visibility into resource usage and promote better tracking and accountability.

As a admin user of meshStack I would like to make sure I am creating the payment method for the correct workspace by seeing the workspace identifier. At the moment only the display name of a workspace is shown and names are not unique inside meshStack.

At the moment the CSV Export from meshStack is using the US style number format. This means that Thousands separator using , and decimal separator . It would be great to either have a dynamic decision based on the settings of the OS / Web Browser location. Or having the option to select which number format to download.