QPR ProcessAnalyzer Upgrade Notes and Known Issues

This page collects everything you need to know before, during and after updating QPR ProcessAnalyzer: known issues in current releases, upgrade and migration notes for each release, and general considerations that apply across versions.

How to use this page when updating:

1. Check known issues for open problems and workarounds that affect the version you are updating to.
2. Read the upgrade and migration notes for every release between your current version and the target version, not only for the latest one.
3. Review general upgrade considerations for requirements that apply across releases, such as runtime, database platform and driver compatibility.
4. Follow the step-by-step update procedure in updating QPR ProcessAnalyzer Server.

QPR ProcessAnalyzer 2026.7.1 (build 11065) (released 22.10.2026)

Known issue: QPR ProcessAnalyzer can become very slow, and the calculation may appear to hang, when a function argument contains many consecutive logical AND (&&) or OR (||) operators. The parser takes a very long time to process such expressions. For example, the following expression is problematic: Function(Column("column") == "value1" || Column("column") == "value2" || Column("column") == "value3" || ...)

This is a remaining case of the earlier known issue, where an expression containing more than five consecutive logical AND (&&) or OR (||) operators could cause QPR ProcessAnalyzer to hang. That issue was fixed only partially, and this note describes the part that is still open: when the consecutive logical operators appear inside a function argument, the parser slows down a lot. The two notes therefore describe the same underlying defect in different contexts, which is why a similar note appears again in this release.

Affected environments: As with the earlier issue, the issue affects both Snowflake models and in-memory models.

Recommendation: Don't update to this release if your expressions use long chains of consecutive logical operators in function arguments. The issue will be fixed in a later release.

Workaround: In some cases, you can avoid the issue by rewriting the expression. For example, enclose each comparison in parentheses: Function((Column("column") == "value1") || (Column("column") == "value2") || ...). Other options are to split a long chain of operators into smaller parts, or to use a different construct that gives the same result. These are the same workarounds as for the earlier issue. If you need help rewriting an expression, please contact QPR CustomerCare.

QPR ProcessAnalyzer 2026.7 (build 11061) (released 14.10.2026)

Known issue: QPR ProcessAnalyzer can hang, meaning the calculation never completes, when an expression contains more than five consecutive logical AND (&&) or OR (||) operators. For example, the following expression is problematic: Column("column") == "value1" || Column("column") == "value2" || ...

Affected environments: The issue affects both Snowflake models and in-memory models.

Recommendation: Don't update to this release if your expressions use long chains of consecutive logical operators. The issue will be fixed in a later release.

Workaround: In some cases, you can avoid the issue by rewriting the expression. For example, enclose each comparison in parentheses: (Column("column") == "value1") || (Column("column") == "value2") || ... Other options are to split a long chain of operators into smaller parts, or to use a different construct that gives the same result. If you need help rewriting an expression, please contact QPR CustomerCare.

QPR ProcessAnalyzer server configuration has been simplified: customized HTTP response headers are now defined only in the appsettings.json file, and equivalent settings in the web.config file no longer take effect.

QPR ProcessAnalyzer Native App now requires the SNOWFLAKE database role ANACONDA_REPOSITORY_USER. Without this role, the business calendar, conformance checking, and clustering analysis don't work. If you use the Native App, see the permission instructions.

QPR ProcessAnalyzer now supports Snowflake ODBC driver 4.x. Support for Snowflake ODBC driver 3.x is retained, so no immediate action is required when updating to this release. However, we recommend upgrading to driver 4.x. For details, see the migration instructions.

QPR ProcessAnalyzer 2026.6 (build 11020) (released 3.9.2026)

Known issue: KPI Card title is not hidden when there is a space character in the Title field in the chart settings. Instead, an automatically generated title is shown. Workaround to hide the title is to use specify a space in the measure's Custom label.

Snowflake has released the Snowflake ODBC Driver 4.x, which is currently in the public preview phase (not aimed for production usage). QPR ProcessAnalyzer is not yet compatible with this version. For QPR ProcessAnalyzer, use the 3.x driver version. More information: https://docs.snowflake.com/en/developer-guide/odbc/odbc-universal-core.

QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

Known issue: QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the PA_CONFIGURATION table contains setting values (CFG_VALUE) stored in non-textual data types. This issue has been fixed by the next release (QPR ProcessAnalyzer 2026.6, build 11020).

To fix the issue for this release, run the following SQL command to convert values to strings:

UPDATE [PA_CONFIGURATION]
SET [CFG_VALUE] = CAST([CFG_VALUE] AS NVARCHAR(4000))

QPR ProcessAnalyzer 2026.2 (build 10897) (released 2026-02-26)

Snowflake user-defined functions (UDF) used by QPR ProcessAnalyzer have been updated to use Python 3.13. Some of the old versions of the functions use Python 3.9 which has been deprecated by Snowflake. Although the old versions are not anymore used by QPR ProcessAnalyzer, they are not automatically deleted and thus Snowflake may send notifications about existing deprecated functions. It's recommended to remove the old functions which are following:

• QPRPA_UDF_BC_DURATION_BETWEEN_DATES
• QPRPA_UDF_BC_DURATION_BETWEEN_DATES_V2
• QPRPA_UDF_BC_DURATION_BETWEEN_DATES_V3
• QPRPA_UDF_BC_DURATION_BETWEEN_DATES_V4
• QPRPA_UDF_BC_DURATION_BETWEEN_DATES_V5
• QPRPA_UDF_BC_DURATION_BETWEEN_DATES_V6
• QPRPA_UDF_BPMN_CONFORMANCE_VIOLATIONS_FLOWS
• QPRPA_UDF_BPMN_CONFORMANCE_VIOLATIONS_FLOWS_V2
• QPRPA_UDF_BPMN_CONFORMANCE_VIOLATIONS_FLOWS_V3
• QPRPA_UDF_BPMN_IS_CONFORMANT
• QPRPA_UDF_BPMN_IS_CONFORMANT_V2
• QPRPA_UDF_BPMN_IS_CONFORMANT_V3
• QPRPA_UDTF_CLUSTER
• QPRPA_UDTF_CLUSTER_V2
• QPRPA_UDTF_CLUSTER_V3
• QPRPA_UDTF_CLUSTER_V4

QPR ProcessAnalyzer 2026.1 (build 10870) (released 2026-01-19)

QPR ProcessAnalyzer Server and QPR ScriptLauncher are running on .NET 10, replacing the previous .NET 8 version. When updating to this release, make sure to install the .NET 10 Runtime (update instructions). While .NET 8 and .NET 10 can run side by side, .NET 8 does not need to be removed immediately. However, for security reasons, any unused .NET 8 installation should be uninstalled as soon as possible after the update.

Known issue: The histogram visualization doesn't work in this release. The issue has been fixed by the next release (QPR ProcessAnalyzer 2026.2, build 10897). Possible workaround is to use the column chart where to set no spacing between columns. This can be configured with the following Custom Layout settings:

{
	"plotOptions": {
		"series": {
			"pointPadding": 0,
			"groupPadding": 0
		}
	}
}

QPR ProcessAnalyzer 2025.7 (build 10821) (released 2025-11-13)

Known issue: Creating case and event attribute filters in dashboards is not possible from the main header for the following types of in-memory models and attributes:

• Any attributes for ODBC loaded models
• Any attributes for Loading script models
• Calculated attributes in any in-memory models.

Workaround is to create the filter rule in a chart's settings and drag-and-drop it to the header. The issue has been fixed by the next release (D-14751). The issue does not concern Snowflake models.

QPR ProcessAnalyzer 2025.6 (build 10690) (released 2025-10-01)

Known issue: If the DefaultUiLanguage system configuration is not defined, users who haven't changed their own language, are unable to login. To prevent this problem, please ensure the DefaultUiLanguage is defined. The next release has fixed this issue (D-14706).

Content-Security-Policy (CSP) HTTP header has been updated to enhance security by implementing more restrictive settings. The following directives have been added:

• object-src 'none'
• frame-ancestors 'self'
• form-action 'none'
• base-uri 'none'
• worker-src blob:

These new restrictions may affect usage that has previously been possible. For example, with the new settings, QPR ProcessAnalyzer can be embedded to a website only within the same origin. For detailed instructions on embedding QPR ProcessAnalyzer on a different website, please refer to this quide. Additionally, for information on modifying the CSP settings, see documentation for security hardening.

In the QPR ProcessAnalyzer 2025.6 Native App, the release version number is not displayed correctly in the User Settings dialog. This omission does not have any other complications. QPR ProcessAnalyzer 2025.6 is the only release with this issue, making it possible to identify this release despite the missing version number. This issue is specific to the Native App only. The next release has fixed this issue (D-14703).

QPR ProcessAnalyzer 2025.5 (build 10361) (released 2025-08-21)

When using Snowflake Cortex, the AI Assistant is not showing the results table in the assistant's response. This issue has been fixed by the next release.