Multiple webook calls overlaping

Hey @mattesilver,

The user management feature changed some parts of the internal API, There are a couple of ways to still use it like the example here: How to authenticate for REST API with Users management activated? - #3 by JulienDelRio

Sorry for the misunderstanding; I don’t have users, just N8N_BASIC_AUTH_USER

Hey @mattesilver,

No misunderstanding at all buddy, The user management feature changed how the internal API works if you are using it or not. That being said I have not tried it without so it could be a similar process where you need to get the token to be able authenticate from the auth request.

Hmm…
the default user has neither email nor password to login with.
I guess I can downgrade back to 0.167 for now?

This is my solution for preventing simultaneous processing while keeping the processing order

2 Likes

Hi Jan! Is this still possible? I cannot figure out how to get running workflows - have the same challenge as OP! Thanks :slight_smile:

Did you try with the example?

1 Like

I did (Multiple webook calls overlaping - #5 by jan) but I got the following error: ERROR: Cannot read properties of undefined (reading 'filter') [Line 1]

I can live with that though, as I would just use the n8n node and try to get running workflows. However, while testing the running workflow doesnt show up. it only shows up once it is finished, but thats not helpful lol :slight_smile:

Am I missing something here? Thanks!

I suspect it failed because the http request that gets the current executions uses the internal api and you may not be authenticating for that.

The public API also doesn’t return running executions so you would need to use the undocumented and unsupported internal API, You can find a workflow that should do that here: Multiple webook calls overlaping - #26 by Tiago_R

I have seen other folk work around this by querying the database directly or using something like Redis to set if the workflow is running already.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.