SaaS customer creating/modifying configurations to Extensions does not persist in the classic Web UI

We're investigating issues for SaaS customers on v1.313.32, making changes to Extension configurations persist when using the Dynatrace classic Web UI. Notable symptoms are when adding new or removing feature sets from an extension, saving appears not to persist, but is properly stored in the backend.

The current workaround to this issue is to use the Extension Manager app to make and save changes.

Alternatively, the configuration API does not present this problem. Please see our documentation for usage:
https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/configuration-api/extensions-api

We apologize for this inconvenience and will continue to update here as we have more information to share.

We have identified the issue within SaaS cluster 1.313.32 impacting the Dynatrace classic UI extension configurations. A hotfix is currently in development.

We will continue to update here as as things progress, thank you for your continued patience while we work towards a resolution.

The hotfix is currently in development, and we’ll keep you posted on its progress.

Thank you for your patience, please continue using the existing workaround and contact Dynatrace Support if you have any questions.

We have begun the rollout of the hotfix to all impacted SaaS clusters. We will continue to update you here as the rollout progresses

Thank you for your patience, please continue using the existing workaround and contact Dynatrace Support if you have any questions.