logicapps SQL Based_SQL Action: Before adding long running scenario query, the workflow is succeeded.

Describe the Bug with repro steps

1.Create a project and add Stateful workflow in VS code.

2.Convert your workflow in SQL Based.

3.Open Designer and add http trigger and sql_Execute query_EXEC wait2;

4.Save, Debug the workflow and run the workflow.

Expected: The workflow should be failed after 2 minutes.

Actual: The workflow is succeeded after 2 minutes and some runs are in running state(when opened the monitoring view shows failed after 10+ minutes).

What type of Logic App Is this happening in?

Standard (VSCode)

Which operating system are you using?

Windows

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "Execute_query": {
                "type": "ServiceProvider",
                "inputs": {
                    "parameters": {
                        "query": "EXEC wait2;"
                    },
                    "serviceProviderConfiguration": {
                        "connectionName": "sql",
                        "operationId": "executeQuery",
                        "serviceProviderId": "/serviceProviders/sql"
                    }
                },
                "runAfter": {}
            }
        },
        "contentVersion": "1.0.0.0",
        "outputs": {},
        "triggers": {
            "When_a_HTTP_request_is_received": {
                "type": "Request",
                "kind": "Http"
            }
        }
    },
    "kind": "Stateful"
}

Screenshots or Videos

Browser

VS Code

Additional context

VS Code extension - 4.71.5

Sep 05 '24 16:09 vgouth

@ccastrotrejo I am facing the issue in portal, not only in Vs Code. I have added bug for the same.

#https://github.com/Azure/logicapps/issues/1167

Sep 16 '24 11:09 AzureDev0012

Issue repro in the latest VS code request

VSIX Version: 4.85.2

Sep 19 '24 11:09 vgouth

Issue repro in the latest VS code request. Getting success with error log.

VSIX Version: 4.96.0

Oct 07 '24 07:10 vgouth

Issue repro in the latest VS code request. Getting success run.

VSIX Version: 4.107.0

Oct 18 '24 11:10 vgouth

Issue repro in the latest VS code request.

VSIX Version: 4.116.7-fixSessions

Nov 15 '24 12:11 vgouth

This issue is stale because it has been open for 45 days with no activity.

Dec 30 '24 13:12 github-actions[bot]

It is in progress

Jan 10 '25 18:01 vgouth

Issue repro in latest VS code test pass.

VSIX version: 5.14.1

Jan 21 '25 06:01 vgouth

Issue repro in latest VS code test pass.

VSIX version: 5.18.5

Feb 14 '25 07:02 vgouth

Issue repro in latest VS code test pass for bundle VSIX Version: 5.18.7

Feb 26 '25 14:02 vgouth

Issue repro in the latest VS code request. VSIX Version : 5.44.5

Mar 13 '25 08:03 vgouth

Issue repro in latest VS code test pass VSIX Version : 5.58.1

Mar 26 '25 17:03 vgouth

Issue repro in latest VS code test pass. Issue repro in nuget artifact as well

VSIX Version: 5.58.4 and bundle artifacts Version: 1.119.7

Apr 17 '25 08:04 vgouth

Issue repro in latest VS code test pass. Issue but not repro in nuget artifact this time

VSIX Version: 5.94.0 and bundle artifacts Version: 1.123.18

May 07 '25 03:05 vgouth

Issue repro in production VSIX. VSIX Version: 5.94.17

May 21 '25 06:05 vgouth

Issue repro in latest VS code test pass. VSIX Version: 5.109.13

Jun 16 '25 05:06 vgouth

Issue repro in latest VS code test pass. VSIX Version: 5.117.3

Jul 01 '25 08:07 vgouth

Issue repro in latest VS code test pass. VSIX Version: 5.130.5

Jul 18 '25 07:07 v-ksruthi

Issue repro in latest VS code test pass. Production VSIX Version: 5.130.9

Aug 06 '25 03:08 vgouth

This issue is stale because it has been open for 45 days with no activity.

Sep 20 '25 04:09 github-actions[bot]

This issue may still persist, since we are currently experiencing a blockage in SQL artifact testing. As mentioned in the previous update by abode, we are skipping these scenarios for now. I am adding comments to the bug to ensure it remains active and visible for further tracking.

Sep 23 '25 05:09 vgouth

This issue is stale because it has been open for 45 days with no activity.

Nov 07 '25 07:11 github-actions[bot]

This issue may still persist, since we are currently experiencing a blockage in SQL artifact testing. As mentioned in the previous update by abode, we are skipping these scenarios for now. I am adding comments to the bug to ensure it remains active and visible for further tracking.

Nov 07 '25 08:11 vgouth

This issue is stale because it has been open for 45 days with no activity.

Dec 22 '25 09:12 github-actions[bot]

This issue was closed because it has been inactive for 14 days since being marked as stale.

Jan 05 '26 09:01 github-actions[bot]