Users are reporting a bug where disabling the “Give this badge more than once” option for SQL-triggered badges is not preventing repeated awards. satonotdead initially reported the issue, having previously experienced problems with badge repetition linked to a previous issue. Michael12 confirmed experiencing the same bug and offered to share their badge SQL. Lilly requested the SQL and screenshots of badge settings from satonotdead and others to replicate the issue and verify configurations screenshots provided. The SQL provided by satonotdead selects users based on gamification scores and awards badges if they haven’s already received them. satonotdead shared images showing the problematic badges being repeatedly granted. JammyDodger questioned whether the issue stems from the SQL query’s attempt to handle multiple awards and referenced previous discussions about these badges previous discussion link. It’s unclear whether the problem is isolated to satonotdead’s instance or a wider bug.
Disabling the option ‘Give this badge more than once’ is not working, at least with SQL-triggered badges.
I have three badges with this option disabled that get triggered automatically many times.
I had a very big issue because of it, so I’m here reporting that this was not an isolated case but probably a buggy behavior.
If possible, please post the badge sql, as well as screenshots of the badge settings, for example these settings:
(moved this topic to Support until we can at least confirm it’s not the config)
Just jumping in here as I’ve run into the same issue. I’ve also disabled the “Give this badge more than once” setting on several SQL-based badges, but they keep getting awarded repeatedly. It would be helpful to know if anyone has found a workaround or if this is confirmed as a bug. I can share my badge SQL, too,o if needed.
please post the sql and your badge settings so i can confirm the configuration is correct and attempt to replicate the issue.
SELECT
gs.user_id,
current_timestamp AS granted_at
FROM
gamification_scores gs
WHERE
(:backfill OR gs.user_id IN (:user_ids))
AND gs.date >= (current_date - interval '1 month')
AND NOT EXISTS (
SELECT 1
FROM user_badges ub
WHERE ub.user_id = gs.user_id
AND ub.badge_id = YOURIDOFBADGE
)
GROUP BY
gs.user_id
HAVING
SUM(gs.score) > 11
I have only selected ‘Show on public badges page’ and ‘revoke daily’. The activator is recurrent daily.
I would still like to see a screenshot, thanks. the reason is I can verify that it is the exact same screen (version) and the settings are the same even with different languages in interface (also a rogue component or plugin may be changing the settings page). for example, I don’t want to just assume “activator” means “trigger” (although I think it does in this case).
That looks like it was a bug with the automation rather than a custom badge?
I remember we talked about these badges before (Amending sample Gamification scoring badge - #2 by JammyDodger). Have they been playing up this whole time, or is this a recent thing?
Without testing, one of the things that looks like it doesn’t belong is the ‘AND NOT EXISTS’ section. Are you trying to handle not awarding multiples within the query itself?
