> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/pos-integration-how-flaik-connects-to-your-pos/pos-integration-api-overview/release-notes/2.5.10.0.md). # 2.5.10.0 ### Installation * [Installation directory](https://drive.google.com/drive/folders/1eTaE-EB3i-c-frJHNvxv-rjGXq_mzI8f) * This release requires both flaik SQL scripts to be run in order. * This release requires all Resort POS SQL scripts to be run in order. ## \[2.5.10.0] - 2025-03-27 This release is the final version of the 2.5.x series, it is recommended for all clients. ### New All POS Types: * Endpoint to allow singular schedule processing. This is preparatory work to allow migration of Instructor schedule sync tasks to a queue-based system as opposed to the current batch system that requires a standalone flaik database on your infrastructure. ### Fixes RTP|One specific * Person Search * Additional checks for RFID # associated to Access Codes * Removed unnecessary calls to the database tables/functions to improve performance * New lookup to handle re-issued tickets Siriusware Specific * Resolving issue where Returns of line items or modifiers in Siriusware could be attributed to a different guest number than originally attributed to. flaik now is able to identify and skip these instances - keeping Sales fetches accurate. * Added the lesson level type tch\_level and set the numeric value associated with it for Ski School Module clients to allow levels to be interpreted more accurately. --- # 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://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/pos-integration-how-flaik-connects-to-your-pos/pos-integration-api-overview/release-notes/2.5.10.0.md?ask=&goal= ``` `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.