Can't make Reply to message in Slack

I’m trying to add a message to the thread, but I can’t see it in the thread.


Is this module not working correctly or am I doing something wrong.

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:

n8n Version 1.29.1
Operating system: Win 11
Running n8n via: n8n cloud

Hi @Oleksandr_Tsap :wave: Welcome to the community :tada:

Have you checked out this response from Jon on how to reply in thread? It might help you out!

Yes, that’s the thing, I’m using the Slack module with this option, but now it’s a little different than what Jon pointed out, and secondly, it’s not working correctly… you can see it in the images above.

It seems that the module does not find a parent message with such a timestamp. At least that’s the behavior.

Hi @Oleksandr_Tsap :wave: And ah, sorry about that :see_no_evil:

Could you share your workflow with us so I can take a closer look? You can hit cmd/ctrl + A and then cmd/ctrl + C while viewing your workflow to copy all nodes, and then stick that in a code block here on the forums :+1: Then I can take a closer look at the error you’re running into :eyes:

2 Likes
1 Like

After some pretty extensive testing, it looks like the thread option may not be working correctly. I’ve reported this over to our engineering team to take a closer look, and you’ll be notified with any updates! :+1:

1 Like

How long can it take to fix this bug?

Hey @Oleksandr_Tsap,

It all depends on priority and how complicated the issue is so it could be fixed in next weeks release or it could be fixed in 3 weeks it all depends really.

1 Like

Is there any update on the bug?

Hey @Oleksandr_Tsap,

It is still waiting to be picked up, I took a quick look a few days ago and oddly enough we appear to be sending the data as Slack document it in their api so I am waiting for a second set of eyes to see if I missed anything.

2 Likes

I apologize for asking so often, but it is very important. Is there a change in my problem?

Hey @Oleksandr_Tsap,

Not yet, I was hoping to have had a chance to sort this by now but I have just not found the time. It is however still waiting to be picked up by someone so this will get sorted I am just not sure when.

1 Like

Thanks @Jon ! I had the same issue and I am waiting for this bug to be fixed to sign up to n8n as its the main use I have for it at the time. Excited that it will be taken care of soon

1 Like

I posted a workaround for this issue here: