How is your experience with the OutSystems Community?
23
Views
4
Comments
Solved
Service Studio Crashes When Adding Input Parameters to Advanced SQL
Service Studio Version
11.55.76 (Build 64944)

Service Studio Crashes When Adding Input Parameters to Advanced SQL

Hi everyone,

I'm experiencing an issue where OutSystems Service Studio crashes unexpectedly whenever I add or reference an input parameter in an Advanced SQL query.

Environment

  • Service Studio Version: 11.55.76.64944
  • Platform Server Version: 11.40.1.46624
  • Environment: erpdstg.hs-ict.co.kr

Issue Description

When editing an Advanced SQL query, Service Studio crashes as soon as I add or reference a query parameter. The crash occurs consistently and is reproducible.

The main exception reported is:

System.InvalidOperationException:Trying to add a Zombie referer: Condition is true

The stack trace indicates that the exception occurs while Service Studio is processing SQL expression references and query parameters:

ServiceStudio.SQLExpressions.AbstractSQLExpression.SetReference()ServiceStudio.SQLExpressions.AbstractSQLExpression.SetReferences()ServiceStudio.SQLExpressions.AbstractSQLExpression.SetSQLExpression()

What I've Observed

  • The crash happens inside the Advanced SQL editor.
  • It occurs when adding, renaming, or referencing query parameters.
  • Service Studio closes unexpectedly before I can save the query.
  • The issue is reproducible with newly created Advanced SQL nodes.

Questions

  1. Has anyone encountered this "Trying to add a Zombie referer" exception before?
  2. Is this a known bug in Service Studio 11.55.76?
  3. Are there any recommended workarounds or hotfixes?
  4. Could this be related to the version mismatch between Service Studio 11.55.76 and Platform Server 11.40.1?

Any help would be greatly appreciated.

Thank you.

2026-06-20 17-43-43
Sherif El-Habibi
Champion
Solution

Hello @SUNGIL CHOI,

For the current situation, you may consider downloading an earlier stable version. I am currently using version 11.5.5 without issues. It has indeed been reported that this version has some issues related to SQL editing.

2025-09-25 14-38-22
Lokesh Kumar Yadav
Solution

This looks like a Service Studio client-side issue rather than a problem with your SQL itself. The Trying to add a Zombie referer exception is usually related to corrupted internal references or a bug in the SQL editor when handling parameter bindings. Since the issue is reproducible even in newly created Advanced SQL nodes, it may be caused by the current Service Studio version or compatibility issues between Service Studio 11.55.76 and Platform Server 11.40.1.

A few workarounds you can try are: clearing the Service Studio cache, republishing dependencies, creating the SQL in a fresh module, or temporarily using a different Service Studio version. Also check whether there are any available patches or newer versions from OutSystems, as this may already be a known bug fixed in later releases. If the issue continues, raising a support ticket with the crash logs would be the best option.

2026-03-27 07-32-35
James Padua

I've seen a few similar posts with the same issue. I believe this has something to do with the latest update. You can try installing previous version of Service Studio from https://www.outsystems.com/downloads/search/Service-Studio/11. Then disable the auto update for a few weeks.

2026-06-20 17-43-43
Sherif El-Habibi
Champion
Solution

Hello @SUNGIL CHOI,

For the current situation, you may consider downloading an earlier stable version. I am currently using version 11.5.5 without issues. It has indeed been reported that this version has some issues related to SQL editing.

2025-09-25 14-38-22
Lokesh Kumar Yadav
Solution

This looks like a Service Studio client-side issue rather than a problem with your SQL itself. The Trying to add a Zombie referer exception is usually related to corrupted internal references or a bug in the SQL editor when handling parameter bindings. Since the issue is reproducible even in newly created Advanced SQL nodes, it may be caused by the current Service Studio version or compatibility issues between Service Studio 11.55.76 and Platform Server 11.40.1.

A few workarounds you can try are: clearing the Service Studio cache, republishing dependencies, creating the SQL in a fresh module, or temporarily using a different Service Studio version. Also check whether there are any available patches or newer versions from OutSystems, as this may already be a known bug fixed in later releases. If the issue continues, raising a support ticket with the crash logs would be the best option.

UserImage.jpg
SUNGIL CHOI

Thank you all for your valuable suggestions and insights.

I really appreciate everyone who took the time to review my question and share their ideas. Your feedback has given me several approaches to explore and has been very helpful in understanding the best way forward.

Thanks again for your support and assistance!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.