[Bug]: Notification Failing on Uniqueness Error (cardsubscription) #724

New Issue

OVERLORD · 2026-02-04T21:06:03+03:00

OVERLORD commented

2026-02-04 21:06:03 +03:00

Originally created by @StephanSkai on GitHub (Jun 5, 2025).

Where is the problem occurring?

I encountered the problem while interacting with the server (Backend)

What browsers are you seeing the problem on?

Chrome

Current behavior

Implemented telegram bot notifications. Successfully received test messages when connecting the telegram url, however on car change (move or comment), I see the following errors in the logs.

2025-06-02T04:41:27.233096811Z
2025-06-02T04:41:27.233148864Z Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot
2025-06-02T04:41:27.233152861Z be matched up with the column names of any attributes in this model (⁠ cardsubscription ⁠).  This probably
2025-06-02T04:41:27.233155585Z means there is a bug in this adapter.
2025-06-02T04:41:27.233157701Z (Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated
2025-06-02T04:41:27.233159761Z in uniqueness errors, then just use an empty array for the ⁠ keys ⁠ property of this error.)
2025-06-02T04:41:27.233162077Z (Proceeding anyway as if these keys weren't included...)

And received no message regarding card change.

Desired behavior

In this situation, I'd expect a valid message to appear in my telegram chat notifying me of card change.

Steps to reproduce

I added my tgram service to notification panel. Tested it and successfully received the test message:

Test Title

This is a test markdown message!

and then tried to make a comment on a card I am subscribed to, or move a card, and failed to receive a message. Checked the logs and saw a bunch of the above logs.

Other information

No response

Originally created by @StephanSkai on GitHub (Jun 5, 2025). ### Where is the problem occurring? I encountered the problem while interacting with the server (Backend) ### What browsers are you seeing the problem on? Chrome ### Current behavior Implemented telegram bot notifications. Successfully received test messages when connecting the telegram url, however on car change (move or comment), I see the following errors in the logs. ``` 2025-06-02T04:41:27.233096811Z 2025-06-02T04:41:27.233148864Z Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot 2025-06-02T04:41:27.233152861Z be matched up with the column names of any attributes in this model (⁠ cardsubscription ⁠). This probably 2025-06-02T04:41:27.233155585Z means there is a bug in this adapter. 2025-06-02T04:41:27.233157701Z (Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated 2025-06-02T04:41:27.233159761Z in uniqueness errors, then just use an empty array for the ⁠ keys ⁠ property of this error.) 2025-06-02T04:41:27.233162077Z (Proceeding anyway as if these keys weren't included...) ``` And received no message regarding card change. ### Desired behavior In this situation, I'd expect a valid message to appear in my telegram chat notifying me of card change. ### Steps to reproduce I added my tgram service to notification panel. Tested it and successfully received the test message: ``` Test Title This is a test markdown message! ``` and then tried to make a comment on a card I am subscribed to, or move a card, and failed to receive a message. Checked the logs and saw a bunch of the above logs. ### Other information _No response_

OVERLORD closed this issue

2026-02-04 21:06:04 +03:00

OVERLORD commented

2026-02-04 21:06:17 +03:00

@StephanSkai commented on GitHub (Jun 5, 2025):

@StephanSkai commented on GitHub (Jun 5, 2025): ![Image](https://github.com/user-attachments/assets/945c5a87-ad3a-4e55-a5a3-ba705174b5ee)

OVERLORD commented

2026-02-04 21:06:26 +03:00

@meltyshev commented on GitHub (Jun 5, 2025):

Hi! Thanks for reporting this.

First of all, this is just a warning. Waterline ORM can't handle uniqueness errors on multiple fields properly, so it can generally be ignored. However, the strange part is that we've already commented out this warning using this patch, so it shouldn't appear in the logs at all. This likely means the patch wasn't applied in your case, even though it should be applied automatically when you run npm install.

Regarding the notifications, have you tried triggering one from a different user? Notifications aren't sent to the user who performs the action. Also, for testing purposes, you can try setting the same Telegram notification URL in the board settings and then move a card. Since per-board notifications are triggered on every board action, you should receive one that way.

@meltyshev commented on GitHub (Jun 5, 2025): Hi! Thanks for reporting this. First of all, this is just a warning. Waterline ORM can't handle uniqueness errors on multiple fields properly, so it can generally be ignored. However, the strange part is that we've already commented out this warning using [this patch](https://github.com/plankanban/planka/blob/master/server/patches/waterline%2B0.15.2.patch), so it shouldn't appear in the logs at all. This likely means the patch wasn't applied in your case, even though it should be applied automatically when you run `npm install`. Regarding the notifications, have you tried triggering one from a different user? Notifications aren't sent to the user who performs the action. Also, for testing purposes, you can try setting the same Telegram notification URL in the board settings and then move a card. Since per-board notifications are triggered on every board action, you should receive one that way.

OVERLORD commented

2026-02-04 21:06:35 +03:00

@StephanSkai commented on GitHub (Jun 6, 2025):

Fantastic. That worked.

Greatly appreciate your help @meltyshev.

@StephanSkai commented on GitHub (Jun 6, 2025): Fantastic. That worked. Greatly appreciate your help @meltyshev.

OVERLORD referenced this issue

2026-02-04 21:49:07 +03:00

[PR #724] [CLOSED] Added Card Archiving Functionality with Documentation Updates #1085

Sign in to join this conversation.