---
title: "Fixes and Known Issues - Spring 2025"
slug: "fixes-and-known-issues-spring-2025"
updated: 2025-03-26T00:30:42Z
published: 2025-03-26T00:30:42Z
canonical: "docs.processmaker.com/fixes-and-known-issues-spring-2025"
---

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

# Fixes and Known Issues - Spring 2025

## Product Fixes and Known Issues

The Spring 2025 release of the ProcessMaker Platform includes a series of important fixes to enhance functionality and improve overall user experience. This update addresses a variety of issues, ensuring smoother performance, greater stability, and improved usability across several key features.

### Version 4.14.0

**Release Date:** March 25, 2025

FixesKnown Issues

**PDF and File Handling**

- FlowGenie now preserves original PDFs, ensuring full usability for preview and download. Previously, PDFs were split into images, limiting reuse and this improvement keeps your files intact and accessible.

**PM Blocks**

- Processes can now be created from templates with locked PM blocks without triggering SQL integrity errors.
- Rich text fields using “Render HTML from a Variable” now display only the intended content and extra curly braces are not added.
- Line Input fields inside nested loop variables now accept and capture user input as expected.

**Case Management and Launchpad**

- Task names in the "All Cases" and "My Cases" lists correctly reflect their associated processes across all pages, ensuring clarity and consistency.
- Users with proper group assignments can now start cases from the Launchpad without any issue, making it easier for everyone to take action as intended.

**API and Process Requests**

- ProcessMaker API now allows requests to be updated from “CANCELED” or “ERROR” to “ACTIVE” without triggering a “Name has already been taken” error—no name change required.

**User Interface and Navigation**

- Zooming beyond 150% on multi-page screens now retains your current page view, ensuring a smoother and more consistent navigation experience.

**Charts and Aggregation**

- The SUM function now calculates correct totals for large numbers, ensuring reliable results regardless of data size.

**Script Execution**

- Scripts now follow the configured timeout and retry settings, preventing unnecessary retries and Script Timeout Exception errors—even for long-running tasks.

The following issues are being investigated and will be addressed in a future update.

- The VarFinder does not retrieve variables from newly created or edited assets due to an issue affecting case creation. The issue is under investigation, and a fix is planned for the next build.
- Select List of type *Collection* returns full objects instead of a single value.
- A "New Input" column appears in the configuration of a RAG collection, but doesn’t display any data. ***Workaround:*** *Avoid using the "New Input" column unless it’s explicitly required and mapped to a valid input field.*
- PLAID package fails to install due to missing `console.php` file and PSR dependency conflict.
- Manual task screens allow editing of Record List data.
- Loops set by Calc can still be modified in the screen.
- Control selection is not highlighted in Slide Show with alternatives A and B.
- Error "Cannot read properties of undefined (reading 'id')" is seen when adding elements via "Drop to add this flow". ***Workaround:*** *Save the process after dropping the element to properly generate IDs.*
- Console errors appear when cancelling a case.
- Task “Due In” property is unexpectedly modified after changes in task loops. ***Workaround:*** *Re-check and reconfigure the Due In value after modifying task loop settings.*
- Server error occurs when creating a chart in Processes I Manage page.
- Task “Due In” property retains old variable value even when "Use Request Variable" is unchecked. ***Workaround:*** *Manually clear the variable field before switching back to a fixed value.*
- Parallel anonymous Web Entries always open the lowest-numbered task. ***Workaround:*** *Not supported. Redesign the process to avoid anonymous web entries in parallel tasks.*