Workflows “stop” listening after few days

[kristus]

Describe the problem/error/question

I have workflows for gitlab with trigger on issue. Workflows worked great. Added 5 more yesterday.
Today the old workflows doesnt work. I open the executions and the latest triggers are from yesterday. But thats incorrect, as gitlab issue triggers every few minutes.
The newer workflows ( listening for same event / trigger ) have them in executions.

When i “re-activate” the workflow, it works again.

Could it be because 15 workflows listen for same event?

What is the error message (if any)?

No error.

Please share your workflow

Irrelevant. Is just pre-made trigger for GL issue

Information on your n8n setup

• n8n version: 1.39.
• Database default: SQLite:
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• **Running n8n via docker **
• Operating system: ubuntu 20.04

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[kristus]

It is provided

[Jon]

Are there any errors in the n8n log or in GitLab for the webhook? The GitLab trigger is webhook based, we register the url with the Gitlab api and they send the events whenever something happens.

When it stops working you could try using something like curl to post some test data to the webhook and see if it appears.

[kristus]

The workflow worked on 2024-06-05. on 2024-06-06 it havnt had any exectuions (and it wasnt the only one).

for

rg "2024-06-06" n8n.log | rg "[Ee]rror"

there is only one result

{"level":"error","message":"The session \"v99evrpdrbs\" is not registered.","metadata":{"file":"abstract.push.js","function":"sendToOneSession","pushRef":"v99evrpdrbs","timestamp":"2024-06-06T09:55:44.910Z"}}

The Gitlab Trigger is the premade node that uses my personal account Access token. not the oath2.

Today again i check the executions. And the workflows from yesterady are not executing.

I click the Test workflow, try the trigger. and it works. I can see the “Lab” execution in the executions.

So i went ahead deactivate and reactivate the workflow. It works again.

TO me it seems that it is somehow capped, and the workflows i activated the latest, are working, the once that were first dont work until reactivated.

Bcs the workflows trigger after reactivation…

What you mean with webhook ? I dont remember setting any webhook for gitlab. It uses the personal Acess Token via the "
GitLab API connection

https://docs.n8n.io/integrations/builtin/credentials/gitlab/?utm_source=n8n_app&utm_medium=credential_settings&utm_campaign=create_new_credentials_modal#supported-authentication-methods

EDIT: I have discovered, that n8n created 15 webhooks using the acess token. So is thsi what you were referring to. How do i find which workflow uses which?
And it then probbaly makes more sense for me to instead of using the Gitlab Trigger, have a webhook so that i dont have 6 webhooks listening for the same event, which is probbaly where the issue is starting no?

[Jon]

Hey @kristus,

It sounds like if there are 16 we may not be cleaning them up properly, Can you stop the workflow, delete all the webhooks in Gitlab then activate the node again and make sure it has created a new one.

Once this has happened keep an eye on it and see if happens again, The good thing about webhook based triggers like the GitLab one is we don’t really do anything other than provide a URL for the other service to post to so in theory it should always be the same unless the instance is crashing but that would cause us to create a new webhook url for GitLab to use.

[kristus]

So also a possible solution is to create the webhooks myself and isnteaf of gitlab trigger add webhook trigger like gitlab.uri/repo-issues and use that for my 10 workflows inteasd of having 10 gitlab webhooks for same thing?