Unhandled exception using SQL activities

[ilcorvo]

Description

I enabled the SQL activities for PostgreSQL and SQL Server.
As soon as I drag & drop the SQL Query activity the following exception is thrown:

StackTrace:
at Microsoft.JSInterop.JSRuntime.GetObjectReference(Int64 dotNetObjectId)
at Microsoft.JSInterop.Infrastructure.DotNetDispatcher.BeginInvokeDotNet(JSRuntime jsRuntime, DotNetInvocationInfo invocationInfo, String argsJson)
at v.endInvokeDotNetFromJS (https://localhost:60734/_framework/blazor.webassembly.js:1:3158)
at Object.Qt [as endInvokeDotNetFromJS] (https://localhost:60734/_framework/blazor.webassembly.js:1:56145)
at https://localhost:60734/_framework/dotnet.runtime.ew19f13umk.js:3:33879
at Fc (https://localhost:60734/_framework/dotnet.runtime.ew19f13umk.js:3:172343)
at wasm://wasm/00b5ba72:wasm-function[288]:0x1f1e1
at wasm://wasm/00b5ba72:wasm-function[219]:0x1c8c7
at wasm://wasm/00b5ba72:wasm-function[210]:0xea32
at wasm://wasm/00b5ba72:wasm-function[247]:0x1d442
at wasm://wasm/00b5ba72:wasm-function[3222]:0xf1178
at wasm://wasm/00b5ba72:wasm-function[2545]:0xc6ca7

After that, I can configure the activity and publish the workflow, but when I run it I see the message “Successfully started workflow,” yet no workflow appears in the instances list.

Steps to Reproduce

Download and use solution from Elsa Server + Studio example.
Configure with the following base packages: Elsa 3.4.2, Elsa.Sql 3.4.2, Elsa.Sql.PostgreSql 3.4.2, Elsa.Sql.SqlServer 3.4.2, Elsa Studio 3.4.0.
Configure code to UseSql:

Run in debug Elsa server
Drag & drop the SQL Query activity => Attached Exception.

Environment

• Elsa Package Version: Elsa 3.4.2, Elsa.Sql 3.4.2, Elsa.Sql.PostgreSql 3.4.2, Elsa.Sql.SqlServer 3.4.2, Elsa Studio 3.4.0 and code from https://github.com/elsa-workflows/elsa-guides branch main.
  Created workflow:
  sql-query.json

[ilcorvo]

The workflow containing a SQL activity doesn't start even if it is created by code.
I created this workflow:

The program starts, and I can see the wf in the definitions list. I can run it, and I can see the message “Successfully started workflow.”, However, no workflow appears in the instances list.

[KnibbsyMan]

Hi @ilcorvo,

That’s strange, can’t say I’ve had this issue before. Out of curiosity, does the same error on drag & drop happen with any other added extension? It’s just that the errors lead me to think it might be Elsa related rather than the SQL extension. Same for the second error, do any other non-sql workflows run?

If I get a chance I’ll follow your steps to reproduce the issue myself and try to see what’s causing this.

[ilcorvo]

Hi @KnibbsyMan,
thank you for looking into this issue: it is very important for my team.
Regarding your questions:
I also added MassTransit, and it works as expected with no d&d issue. Same goes for many other activities (http, etc.) that we use to build complex workflows.

[KnibbsyMan]

Hi @ilcorvo,

Not a problem. Thanks for the additional information.

As I said, ill try and reproduce the issue from your steps when I get the chance. It does seem strange that it seems to happens only with the SQL Activities though.

For what its worth, I have just been testing some unrelated updates on the 3.6.0 Dev branch using the SQL activities and all seems to working as expected with d&d and when running tests (new 3.6 feature), however I am getting some weird workflow run issues with Elsa Studio. This could be unrelated but I'll do some digging.

[ilcorvo]

Hi @KnibbsyMan ,

I’ve now re-tested the issue using newer versions as well:

• Elsa 3.5.3 (stable)
• Elsa 3.6.0-rc2 (prerelease)

This time I used only Elsa.Sql.SqlServer - avoiding to use Elsa.Sql.PostgreSql package - to test only the critical path for me.

Unfortunately, in all versions the is still an issue. As soon as I drag & drop a SQL Query activity in Elsa Studio, I consistently get a client-side exception and Visual Studio debugger stops on

blazor.webassembly.js

If I continue execution, it is possible to configure the activity, publish the workflow and run it successfully.

To help with troubleshooting, I’ve attached the client log file containing the full error details and stack traces observed during drag & drop and workflow execution. Hopefully this provides more insight into what’s going wrong on my side.

localhost-1768492852123.log

localhost-1768485201757.log

Please let me know if there’s anything else I can try or capture to help narrow this down. This functionality is quite critical for our use case, so I really appreciate you looking into it.

Thanks again 🙏