---
title: "Release 5.19.5"
description: "Fast Line Pro shows a clear banner when its AI service is unavailable and no longer gets locked out by repeated failed connections; saving scenarios through an MCP key works again."
---

# Release 5.19.5

Release 5.19.5 includes all changes of releases [5.19.1](/en/releases/5.19.1.md), [5.19.2](/en/releases/5.19.2.md), [5.19.3](/en/releases/5.19.3.md) and [5.19.4](/en/releases/5.19.4.md). New in 5.19.5: Fast Line Pro now tells you clearly when its AI service cannot be reached instead of showing an empty list, and scenarios can again be saved and restored through an MCP key.

## Fast Line Pro

**New**

- **A banner about the state of the AI service.** If the Fast Line Pro AI service is not configured on the instance, rejects the connection or is temporarily unavailable, every Fast Line Pro screen now shows a banner with a short explanation and, where it is known, the time until which the service is expected to be unavailable. Previously the agent list simply turned empty, and it was not clear whether the agents were gone or the service was down.

**Improved**

- **Repeated failed connections no longer lock the AI service.** When the connection to the Fast Line Pro AI service fails, the system now pauses its attempts instead of retrying again and again, so the service account does not get blocked for a whole day. Instances whose connection works normally are not affected.
- **Clear error messages instead of technical ones.** When the AI service is unavailable, Fast Line Pro screens, knowledge base export and import, and the Fast Line Pro step in scenarios now return an understandable message. In a scenario, such a step quickly moves to its error branch instead of waiting.
- **Internal stability improvements** for diagnosing connection problems with the Fast Line Pro AI service.

## Scenario Builder

**Fixed**

- **Saving a scenario through an MCP key works again.** Saving a scenario with changes, saving separate sections and restoring a version through an MCP key ended with the error "Failed to create save log", and nothing was saved. Saving and restoring now work; in the scenario version history, the author of such changes is the technical user of the MCP key. Saving in the Constructor in the browser and through the AI Assistant has not changed.

## Related documentation

- [Fast Line Pro interface](/en/fastlinepro/explanation/fastline-pro-interface.md)