Run With Payload giving Failed Notification Even when Run Occurs

[daviburg]

Describe the Bug with repro steps

See repro screen capture video below - start a workflow which HTTP request response will return a failure. Portal incorrectly claims that the workflow start failed, when the run did happen.

What type of Logic App Is this happening in?

Consumption (Portal)

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

No response

Screenshots or Videos

Browser

Chrome

Additional context

No response

[Eric-B-Wu]

@daviburg this may be an issue on the backend. Taking a look at the network logs, when we send out the "run with payload" it returns a 400 with no response/error message. In terms of the frontend we can only notify based on the response we get from the backend, and given that the request status is "errored", this may be needed to be changed on the backend to give the right response if a workflow run does start

[daviburg]

@daviburg this may be an issue on the backend. Taking a look at the network logs, when we send out the "run with payload" it returns a 400 with no response/error message. In terms of the frontend we can only notify based on the response we get from the backend, and given that the request status is "errored", this may be needed to be changed on the backend to give the right response if a workflow run does start

Discussed offline to clarify - Eric updated the issue title accordingly, and is investigating how to provide a reliable outcome message about the run scheduling when the run is with payload.