ReleaseBytes
gcp Google Cloud release notes ·

Apigee UI Fixes ServiceCallout Policy and Developer Attribute Saving Issues

gcpgaengineer
patch

The Apigee UI has received bug fixes addressing issues with the ServiceCallout policy and developer custom attributes. Users can now reliably add ServiceCallout policies without encountering disabled 'Create or Add' buttons, resolving a problem where required HTTP target fields were sometimes omitted. Additionally, changes to developer custom attributes in the Apigee UI now save consistently, fixing an intermittent failure where updates would not persist despite reporting success. These fixes improve the usability and reliability of API proxy configuration and developer management within the Apigee UI.

Fixes (2) ›
  • Apigee UI

    Bug ID Description 543626585 ServiceCallout policy can now be added in the Apigee UI Adding a ServiceCallout policy in the Apigee UI no longer leaves the Create or Add button disabled. Previously, selecting Service Callout in the Create policy or Add policy panel could display only the Name and Display name fields and omit the required HTTP target field. With the required field missing, the form never became valid, so the Create or Add button stayed disabled no matter what you entered. This affected both API proxies and shared flows. The earlier workaround of creating a placeholder policy and

    ServiceCallout policyAttach and configure policies in the UI
  • Apigee UI

    Bug ID Description 540008387 Developer custom attributes now save reliably in the Apigee UI Saving changes to a developer in the Apigee UI in Cloud console no longer intermittently fails to persist that developer's custom attributes. Previously, the UI reported the save as successful, but the previous attribute values reappeared when the page was reloaded. Developer updates made with the Apigee API were not affected.

    Apigee UI in Cloud console
Read the original announcement →

https://docs.cloud.google.com/release-notes#August_22_2026

Related releases