Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logic app standard HTTP action sent duplicate POST request without any reason (returns simply success of the second call) #1136

Open
spulkkinen opened this issue Aug 16, 2024 · 4 comments

Comments

@spulkkinen
Copy link

spulkkinen commented Aug 16, 2024

Describe the Bug

The HTTP connector of the Logic App has sent an HTTP request (to the function) twice in a row (no failure in either of the function calls, and there is not even a retry policy in the HTTP action). In the run history, it only shows one action call without errors or retries, with the duration of the action spanning from the start of the first request to the end of the second one. The action also simply returns the response from the second HTTP request with success status code. No trace of any retries in the run history for that action (retry policy is set to none and no loops etc. or any other errors in the run).

LogicAppActionOutputs

On the other hand, the logs of the Azure function called by the HTTP action show traces of two requests coming from the same workflow run (we track in application insights the workflow run id among other things).

DuplicateCalls

Each of the function calls has taken approx. 30s so there is no timeout issues. We can see from AppRequests table that both calls have returned 200 success.
image

So far, this is just an isolated case, usually there are no problems (with hundreds of successful runs).

Plan Type

Standard

Steps to Reproduce the Bug or Issue

Only happened couple of times, hard to reproduce. Seems to happen at random: if the workflow run is retriggered, everything goes without problems.

Workflow JSON

Action in question
{
"type": "Http",
"inputs": {
"uri": "@{parameters('ContractIntegrationFunctionURL')}",
"method": "POST",
"headers": {
"x-functions-key": "@{parameters('ContractIntegrationFunctionKey')}"
},
"body": "@Body('HTTP_POST_LTINT773GetContractReferenceDataFunction')",
"retryPolicy": {
"type": "none"
}
},
"runAfter": {
"HTTP_POST_LTINT773GetContractReferenceDataFunction": [
"Succeeded"
]
}
}

Screenshots or Videos

Additional context

This is a business critical process where function creates data to target (contract to D365 FO). In no circumstances POST requests should be sent several times (unless requested by the retry policy). Please investigate to locate the root cause.

@spulkkinen
Copy link
Author

The issue has unfortunately reappeared, now in production environment.

@spulkkinen spulkkinen changed the title Logic app standard HTTP action sent duplicate request without any reason or trace (returns simply success of the second call) Logic app standard HTTP action sent duplicate POST request without any reason or trace (returns simply success of the second call) Sep 13, 2024
@spulkkinen spulkkinen changed the title Logic app standard HTTP action sent duplicate POST request without any reason or trace (returns simply success of the second call) Logic app standard HTTP action sent duplicate POST request without any reason (returns simply success of the second call) Sep 13, 2024
@maciekak
Copy link

We have the same issue in production environment, actually it happened two times last week. Http action in logic app standard sends 2 requests, but it shows that action was invoked only once.
Requests are handled by azure function, and handling each duplicated request takes around 1 second, but action in logic app that sends duplicated requests takes around 11 seconds (not duplicated actions takes around 1 second).

Copy link

github-actions bot commented Dec 6, 2024

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

@github-actions github-actions bot added the stale label Dec 6, 2024
@andaug
Copy link

andaug commented Dec 10, 2024

Hi, we are seeing the same issue, any update on this, it causes serious issues for us.

@github-actions github-actions bot removed the stale label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants