Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mattermost Get All Reacts fails on 6.3 #2740

Closed
chberti opened this issue Jan 31, 2022 · 3 comments
Closed

Mattermost Get All Reacts fails on 6.3 #2740

chberti opened this issue Jan 31, 2022 · 3 comments
Labels
in linear Issue or PR has been created in Linear for internal review node/issue Issue with a node Released

Comments

@chberti
Copy link

chberti commented Jan 31, 2022

Describe the bug
I recently updated my mattermost instance from 5.X to 6.3. We use N8N as a mattermost bot to automate things.
One workflow we use gets all Reactions on a specific POST_ID. Since the update, getting all reactions on posts that do not contain any outputs an error on this node (continue on fail parameter does not work).
I do not know if this is more related to n8n or to mattermost though. I did not find any documentation on this 'bug'
on either of them.

Thank you in advance ! :)

To Reproduce
Steps to reproduce the behavior:

  1. set up a running mattermost 6.3 instance
  2. post a message in a channel
  3. Use Get all reactions on the post ID
  4. If no reaction present, will get a "Cannot read property '$error' of null"

Expected behavior
mattermost node should output an empty item in this case.

Environment (please complete the following information):

  • OS: CentOS
  • n8n Version 0.157.0
@Joffcom Joffcom added the node/issue Issue with a node label Mar 21, 2022
@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Jan 17, 2023
@Joffcom
Copy link
Member

Joffcom commented Jan 17, 2023

Just adding that internally we are are tracking this as NODE-41

@Joffcom
Copy link
Member

Joffcom commented May 13, 2024

👋🏻 sorry for the delay on this one, I am going through some older issues at the moment and have just put in a PR to fix this which once reviewed should be available in the next release.

@janober
Copy link
Member

janober commented May 15, 2024

Fix got released with [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review node/issue Issue with a node Released
Projects
None yet
Development

No branches or pull requests

3 participants