> ## Documentation Index
> Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fusion 5.19 patch releases

This page lists all patch releases for Fusion 5.19, starting with the most recent. For the 5.19.0 minor release, see [Fusion 5.19.0](https://doc.lucidworks.com/docs/5/fusion/release-notes/5.19/5.19.0-release-notes.md).

To get notified when new Fusion 5.19 patch releases are published, select the **RSS** icon at the top of this page and add the feed to your RSS reader.

**5.19.1**

November 16, 2026

Released on November 16, 2026, Fusion 5.19.1 is a [patch release](https://doc.lucidworks.com/docs/policies/lifecycle-policies/lw-semantic-version-support-lifecycle.md#patch-release-support-policy) that delivers bug fixes for stray content deletion in upgraded AWS S3 Pro and JDBC V2 datasources and for intermittent API Gateway errors.

## Bug fixes

### Upgrading turned on stray content deletion for AWS S3 Pro and JDBC V2 datasources that had it turned off

In Fusion 5.19.0, upgraded or imported AWS S3 Pro and JDBC V2 datasources deleted stray content even when they had turned it off before Fusion 5.18, with the `enableStrayContentDeletion` property for AWS S3 Pro, or with the `strayContentDeletionEnabled` property or a delta query for JDBC V2. Fusion 5.19.0 reads only the `coreProperties.strayDeletionSettings.enableStrayDeletion` property, which defaults to `true`.

Fusion 5.19.1 copies the earlier setting to the `enableStrayDeletion` property when the `connectors-backend` service starts and whenever an AWS S3 Pro or JDBC V2 datasource is created or updated. If the `enableStrayDeletion` property is already set, Fusion 5.19.1 doesn't change it, and logs a warning when it's `true` but the earlier setting turned stray content deletion off. For details, see [Keep stray content deletion turned off for AWS S3 Pro and JDBC V2 datasources](https://doc.lucidworks.com/docs/5/fusion/operations/fusion-5-upgrades.md#keep-stray-content-deletion-turned-off-for-aws-s3-pro-and-jdbc-v2-datasources).

### The API Gateway intermittently returned HTTP 500 errors

In previous versions of Fusion, the API Gateway could reuse a connection to a Fusion service after the service had closed it because it was idle. The request then failed with an HTTP 500 response and a `Connection prematurely closed BEFORE response` message, and the service never received the request.

Fusion 5.19.1 closes idle API Gateway connections to Fusion services after 20 seconds, before the services close them, so requests no longer fail this way.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.