Known Issues
Throughout the development lifecycle of PaletteAI, known issues may arise that affect the user experience. Use this page to review and stay informed about the status of known issues in PaletteAI. As issues are resolved, this page is updated.
Active Known Issues
The following table lists all known issues that are currently active and affecting users.
| Description | Workaround | Publish Date | Product Component |
|---|---|---|---|
| Infrastructure and Fullstack Profile Bundles cannot be shared outside of the scope in which they are created. The Palette cluster profiles are synced to the Project specified by that scope's Palette integration, and cannot be accessed by other Palette Projects. | None available. | July 22, 2026 | ProfileBundle |
| System-scoped Compute Configs cannot be shared with Tenants. Tenant-scoped Compute Configs are referenced by name only, therefore they must be in the same namespace as the Tenant. | None available. | July 22, 2026 | Compute Config |
| Deploying multiple App or Model deployments into the same namespace in the same Compute Pool will cause one or more of the deployments to fail. | Use dedicated namespaces for each deployment. Set either the Target Namespace, or the Workload Namespace variable to a unique value, depending on the Profile Bundle being used. | July 22, 2026 | Application and Model Deployment |
| Changing the ProjectUID of a Palette integration will cause existing Profile Bundles and Compute Pools to become unusable. | For Profile Bundles cloned from built-in profile bundle templates, delete the cloned Profile Bundles from the affected scope. They will be automatically recreated and synced to the correct Palette Project. For other Profile Bundles and Compute Pools: None available. | July 22, 2026 | Palette Integration |