> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-55.02/commander-55.02.11-release-notes/whats-new-in-release-55.02.11.md).

# What's New In Release: 55.02.11

<h2 align="center">Release Summary</h2>

The Verifone Commander Release 55.02.11 delivers improvements to system stability and reliability: back-office reporting is now more efficient with controlled request processing and improved memory management; database connection handling has been redesigned to eliminate checkout lockups and keep the system stable under heavy use; the auto-upgrade process is now more resilient with extended timeouts, better error handling, and clearer guidance to ensure smooth upgrades; and end-of-day processing is more dependable with stronger error recovery and a self-healing network connection that no longer requires a reboot to resolve brief interruptions.

<h2 align="center">Resolutions</h2>

### POS System

1. A back-office system was sending too many stylesheet-based report requests at once, and when user connections timed out mid-request, the system failed to clean up properly, causing files to pile up and memory usage to spike. This was resolved by processing these reports one at a time (queuing instead of running them all at once) and by improving the cleanup process so resources are released properly, even when something is incorrect. (137529)
2. Users experienced checkout lockups and possible data errors because of an outdated method the system used to manage database connections. Under heavy use, too many processes got backed up waiting their turn, which slowed down how quickly connections could be released and picked back up. This was resolved by redesigning how connections are obtained and released so they no longer compete with each other, plus adding extra safeguards to keep the system stable when multiple processes run at the same time. (135650)
3. During a software auto-upgrade at a site, the process took over two hours because the monthly reporting period had never been closed in several years, causing the data backup file to increase over 500,000 records and exceed the upgrade's 30-minute restore timeout — triggering repeated retry attempts that added to the delay. Another issue also caused the system to reject a small number of fuel records with an unrecognized product identifier, and when the restore timed out, it would restart from the beginning rather than picking up where it left off. The resolution includes a software correction to properly handle those invalid fuel records, an increase of the restore timeout from 30 to 60 minutes, and updated upgrade instructions along with a KB Article advising sites to **close their yearly report before initiating an upgrade** if monthly periods have not been closed in a long time. (134040)

### Sales

Users could not close out their end-of-day processing because it kept getting cancelled, caused by an error in the online age verification step combined with a brief network connection loss. This was resolved by handling the errors better during sales processing, and making the network connection more resilient to recover from these brief losses on its own, without needing a system reboot. (136679)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications/commander-55.02/commander-55.02.11-release-notes/whats-new-in-release-55.02.11.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.