Custom trigger receiving empty payload on unsubscribe

Forum|Forum|4 years ago
July 31, 2021
5 replies
1167 views

basdebruin
Community Expert

Hi all,

Wondering if you experience the same. In a custom trigger I have defined the subscribe / unsubscribe endpoints. When the user makes a change to the recipe monday will go through the unsubscribe and then subscribe events. All works fine until my endpoint send a non-200 status from my unsubscribe endpoint. Monday will fail obviously, no problem.

Any successive call monday make to my unsubscribe endpoint for that recipe contains an empty payload.

I am discussing this with the appsupport team but wanted to know if you experience the same. Look like this bug is introduced in the weekend of July 24.

This topic has been closed for replies.

AlexSavchuk
monday.com Team Member
Forum|Forum|4 years ago
August 2, 2021

Hey @basdebruin,

As we’d discussed over email, we are already investigating this issue and will revert back as soon as this is resolved. Thank you for your patience here 🙂

-Alex

Like

basdebruin
Author
Community Expert
Forum|Forum|4 years ago
August 3, 2021

hi @AlexSavchuk

I got an answer and apparently your dev team doesn’t think this is a bug. Sending an empty payload in a post to an unsubscribe endpoint is (in my opinion) a clear bug.

How to continu from here?

Like

AlexSavchuk
monday.com Team Member
Forum|Forum|4 years ago
August 4, 2021

@basdebruin

I see you are working closely with Helen on this issue via email, and it seems like both you and our team are still investigating the behavior. I appreciate your patience and cooperation here, and we’ll get back to you via email as soon as we find out more, as I think that would be the best channel of communication in this case.

I hope this makes sense. 🙂

-Alex