---
title: Regular channel changelog
description: Version 21659.5
component: pingoneaic
page_id: pingoneaic:release-notes:regular-channel/version-21659.5
canonical_url: https://docs.pingidentity.com/pingoneaic/release-notes/regular-channel/version-21659.5.html
llms_txt: https://docs.pingidentity.com/pingoneaic/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
section_ids:
  12_may_2026: 12 May 2026
  changed_functionality: Changed functionality
---

# Regular channel changelog

|   |                                                                                                                                                                 |
| - | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | This is a changelog entry for version 21659.5. You can review the changelog for all versions in [Regular channel changelog](../regular-channel-changelog.html). |

## 12 May 2026

**Version 21659.5**

### Changed functionality

* Graceful shutdown of identity management services (OPENIDM-19536)

  **What changed?** When an identity management service instance shuts down, it now drains in-flight HTTP traffic before exiting. In-flight responses include a `Connection: close` header that signals clients to close persistent (keep-alive) connections.

  **Why it matters?** Previously, integrations that held long-lived connections through a connection pool sent a request over a connection to an instance that had already shut down, which resulted in transient `404` responses or connection errors. With this change, compliant HTTP clients close affected connections and reconnect on the next request, which eliminates those transient failures during routine restarts and upgrades.

  **What you need to do?** Nothing, in most cases. Standard HTTP client libraries and connection pools honor the `Connection: close` header, by default. If you maintain a custom HTTP client or have explicitly disabled connection-close handling, verify that your client respects `HTTP/1.1` connection-close semantics.