Workflow with Slack trigger becomes unresponsive.

[ZanBlayde]

Describe the problem/error/question

I have a slackbot which uses n8n as its back end brain to handle all workflow functions. Randomly the slackbot becomes unresponsive and no executions show up in the n8n logs. I've opened a ticket with slack who have been unable to find an issue on their end. Today, after the slackbot became unresponsive, I set the workflow to inactive, then active again and the slackbot became responsive again.

However, within the same workflow I have a daily scheduled trigger that cleans up a supabase table and continues to work when the slackbot is not.

What is the error message (if any)?

There are no logs available when this happens. Based on the description above, I suspect the issue might be with the slack trigger as the other trigger in the workflow continues to function. I also have a Google Appscript hitting a webhook trigger that continues to work as well.

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Debug info

core

• n8nVersion: 1.75.3
• platform: npm
• nodeJsVersion: 20.18.2
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: community

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 720 hours
• maxCount: 25000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/133.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-02-21T21:11:48.640Z}

[Joffcom]

Hey @ZanBlayde,

We have created an internal ticket to look into this which we will be tracking as "GHC-925"

[ZanBlayde]

I'd also like to note I've experienced this same issue on cloud and self hosted.

[Joffcom]

Hey @ZanBlayde

When it fails does Slack show an error in the app? Next time it happens can you also try and make a curl post to the url to see what is returned, there is no reason for the node to stop working if there are no changes being made so this could be tricky to track down.

[ZanBlayde]

Unfortunately there are no errors in app displayed. I will attempt a curl next time it happens.

…

On Fri, Feb 21, 2025 at 2:34 PM Jon ***@***.***> wrote: Hey @ZanBlayde <https://github.com/ZanBlayde> When it fails does Slack show an error in the app? Next time it happens can you also try and make a curl post to the url to see what is returned, there is no reason for the node to stop working if there are no changes being made so this could be tricky to track down. — Reply to this email directly, view it on GitHub <#13435 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH54ZRS6YVOAIVPPZGADDLD2Q6LUVAVCNFSM6AAAAABXUD5EZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZVGU4DSMBYGU> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: Joffcom]*Joffcom* left a comment (n8n-io/n8n#13435) <#13435 (comment)> Hey @ZanBlayde <https://github.com/ZanBlayde> When it fails does Slack show an error in the app? Next time it happens can you also try and make a curl post to the url to see what is returned, there is no reason for the node to stop working if there are no changes being made so this could be tricky to track down. — Reply to this email directly, view it on GitHub <#13435 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH54ZRS6YVOAIVPPZGADDLD2Q6LUVAVCNFSM6AAAAABXUD5EZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZVGU4DSMBYGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

I had kind of expected Slack to show a connection error where you update the url.