You are viewing limited content. For full access, please sign in.

Question

Question

Details of Workflow 12.0.2605.385 Improved Performance Item

Workflow Version 12 Self-Hosted
Updated June 26
asked on June 16

I noticed in the Workflow 12.0.2605.385 release this bullet point:

  • Improved performance of query-related activities to prevent unexpected delays with certain data source configurations.

I was wondering if someone could give more details about this?

0 0

Answer

SELECTED ANSWER
replied on June 17

Data queries using custom connection strings were a couple of seconds slower on average than data sources using the built-in direct connection setup. 

3 0

Replies

replied on June 17

Hi Blake, is this question related to the posted Laserfiche 12 Changelog fixes? (625064)
May 18, 2026: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/intro-laserfiche-12-changelog.htm
I ask as related April video link covers Cloud and AI features

0 0
View 6 previous replies
replied on June 17

Hi Paul, yes, it is related to the May 18, 2026, changes for Workflow.

0 0
SELECTED ANSWER
replied on June 17

Data queries using custom connection strings were a couple of seconds slower on average than data sources using the built-in direct connection setup. 

3 0
replied on June 20

Since installing this version on a fresh install we get an error on all custom queries both on imported workflows and when creating a custom query from scratch to declare the variable for any parameters that are used in the custom query.

An upgraded install does not have the same issue

0 0
replied on June 22

Hi Sonja,

We need additional information (e.g. the data source type and the custom query WF activity definition) to look into this issue. Could you please open a support ticket for this issue?

0 0
replied on June 22

Hi Zihang

 

We have two servers with LF12 installed.  The one was upgraded from the initial install we did early 2025, this one had no issue.

The second was a fresh install for out test environment with a new databases created and testing a single workflow with no other traffic on the network failed.  

I resolved the issue by backing up the database from the live environment that is functioning correctly as expected and then restoring it to test and changing the connection to the test SQL instance.

Both servers are Windows 2022 servers connecting to SQL 2022 on a Windows 2022 server installation.

I made a backup of the clean database created during the install as well.

The issue seems to only happen with a brand new install and databases creation.

0 0
replied on June 22

Hi Sonja,

We are investigating the issue; however, we have not been able to reproduce it in our internal testing environment after brand new install. 

To assist us in troubleshooting, could you please provide the following information?

  • The error message shown on Workflow Designer when the custom query activity using variable for parameter failed
  • The workflow definition (exported as a .wfi file) that includes the failed custom query activity
  • Workflow logs (C:\Program Files\Laserfiche\Workflow\Logs) captured at the time the error occurs

 

As the files may be large or contain sensitive data, we recommend opening a support ticket instead of posting them on the public Answers. Thank you for your assistance.

0 0
replied on June 22

Hi Zihang

 

Thanks for the update.  I will open a support ticket with the required information.

 

Best Regards

Sonja

1 0
replied on June 25

Wondering if any progress has been made on Sonja's issue?

0 0
replied on June 26

No case was raised with Laserfiche Support for Sonja's issue. 

0 0
replied on June 17

I've had issues when doing large migrations involving database lookups whereby the query performance degrades significantly over time, i.e. from a few hundred milliseconds to over an hour to complete a simple SQL lookup. I've seen it across multiple sites now but not in all cases. Using smaller batches helps but performance still degrades to the point a huge backlog is created. I wonder if this fix may address this? 

 

0 0
replied on June 22 • Show version history

Hi Nigel,

This issue is unlikely to be related. It appears to be caused by a high load on the SQL Server or Workflow Server, but we need additional information to reach a solid conclusion.

To help us better understand the situation, could you please clarify the following:

  • When the performance degradation occurs, does running queries directly in SQL Server Management Studio also become slow, or is the slowness limited to workflow‑executed SQL queries?
  • The phrase "large migrations involving database lookups" was mentioned — could you clarify what the migration refers to? Is it performed by the Workflow system or by another product?
  • Approximately how many workflow instances are running when the performance degradation occurs?
    • Out of those, how many workflows include SQL query activities?

 

Thank you for providing this information. We recommend opening a support ticket so you can share more detailed information with us.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...