The workflow sets the loading state with assistant.threads.setStatus, runs a long task, and finally posts a Slack message to clear the loading. Most of the time it works, but sometimes the loading indicator disappears immediately, even though the task is still pending. This leaves the user with no loading state visible for a few seconds, until the final reply arrives.
Has anyone else experienced this intermittent behavior when using the Slack + Thinking UI pattern in n8n? Any suggestions on how to ensure the loading stays visible until the final message is sent?
I’m facing the same issue too — sometimes the loading indicator clears too early even though the task is still running. Would like to know if there’s a reliable fix or workaround for this.
Seeing the same behaviour here, it isn’t specific to n8n as it happens if you make the call via curl. It’s more a flaw or design decision in the new Slack setStatus API.
It appears this resets after 2 minutes, so if the task takes longer than this your status will be cancelled.
I’ve reported the issue to slack, will report back what they say.
I think it needs an additional parameter to the API for the developer to be able to specify a clear_after or timeout value that is appropriate to the use case.