Issue After Upgrade to 7.4 – Error When Using "Find References" (@retired variable already declared)

[kantasit]

The variable name '@retired' has already been declared.
Variable names must be unique within a query batch or stored procedure.

This happens when right-clicking an action on an object and selecting “Find References.”
It does not seem related to any logic in our own automations.

What We’ve Investigated:

• The stack trace shows the error comes from:

  BluePrism.AutomateAppCore.IServer.GetReferences

  → Which suggests this is an internal Blue Prism SQL query, not something we’ve created.

• We ran the following query on our Blue Prism database to check for duplicates:

  sql

  SELECT OBJECT_NAME(object_id), definition FROM sys.sql_modules WHERE definition LIKE '%@retired%'

  → Result: 0 rows — no procedures, views, or functions use @retired.

This confirms the error likely originates from Blue Prism’s internal metadata handling during the reference scan.

Currently, we are avoiding the use of “Find References” to prevent client crashes until a solution is found.

Questions

1. Is this a known issue in BP 7.4.0?

2. Has it been resolved in any subsequent 7.4.x patch?

3. Is there any way to resolve or patch this internally?

We’d appreciate any guidance or confirmation.
Happy to provide logs or more technical details if needed.

Thanks in advance!

Best Regards,
Kantasit

[steven.boggs]

Hi Kantasit,

I've checked on this internally and can confirm our Product team are aware of this issue and are currently investigating it, with a fix request logged against v7.4 of BPE. Currently there are no timelines for when this fix is slated to be included in an upcoming release but we'd recommend keeping an eye out for future release notes updates on it.