Any reason the badge query preview would read: 91 badges to be assigned. But the badge never gets assigned. How can this be?

Good news, everyone. :goodnews: I got a query to work. I wrapped my original query in: SELECT DISTINCT(user_id), CURRENT_TIMESTAMP granted_at FROM (my existing query here) AS top_answerers WHERE (:backfill OR ( user_id IN (:user_ids) )) So in this case, the multiple user_ids was the issue. I guess users won’t be able to get this badge multiple times, but I can live with that for now.

Backlog badge assignments run daily

If you don’t want to wait, visit /sidekiq/scheduler and click Trigger on Jobs::BadgeGrant.

@sam even though backlog badge assignments run daily, shouldn’t the badge still be assigned at some point? The query proved to work in postgres (identifying user’s who should be receiving the badge) and the preview query has listed the number of badges to be assigned weeks ago yet 0 have been given. This is the query (let me know if the backfill might be screwing me up): SELECT topics.id AS topic, posts.id AS post_id, users.id AS user_id, users.title, MAX(posts.like_count) AS like_count, CURRENT_TIMESTAMP granted_at FROM topics JOIN posts ON topics.id = posts.topic_id JOIN users ON users.id = posts.user_id WHERE posts.like_count > 0 AND users.title = 'Real Estate Agent' AND (:backfill OR ( users.id IN (:user_ids) )) GROUP BY topics.id, posts.id, users.id, users.title HAVING MAX(posts.like_count) >= (SELECT MAX(p.like_count) FROM topics t JOIN posts p ON t.id = p.topic_id JOIN users u ON u.id = p.user_id WHERE t.id = topics.id GROUP BY u.id order by max desc limit 1) ORDER BY MAX(posts.like_count) DESC The settings are set as below: [תמונה]

@fefrei thanks for this. I did just use /sidekiq/scheduler for the first time because your suggestion. Really great tool, however, my badge is still not being assigned. It is so odd because I would think if the preview query lets me know that X amount of people are set to get the badge, and then I run Jobs::BadgeGrant …you would think the badge would definitely be assigned afterwards, but still 0. :persevere:

@sam UPDATE: upon looking at /logs I see this error: Job exception: ERROR: duplicate key value violates unique constraint "index_user_badges_on_badge_id_and_user_id_and_seq" DETAIL: Key (badge_id, user_id, seq)=(118, 139, 0) already exists.

You have a query that is targetting posts there no? If not, you need to be selecting distinct user ids, looks like you are selecting dupes.

Can’t a badge be given more than once though? The query gives a badge for the person with the most likes on a post in a topic (if they are part of a particular group). A person could achieve this on multiple topic threads, thus their user id would appear more than once in the query.

In that case you want to return the post_id cause then you associate the badge with a post.

Hate to be a pain but even by using (:backfill OR ( posts.id IN (:post_ids) )) instead of relating the user_id doesn’t do the trick. I am mostly frustrated because if the preview says its working, why shouldn’t it give those users the badge? :persevere:

Err, wait a second, what do you think that query is actually doing? Also, you need to make the (user_id, post_id) pairs unique or you crash the grant. The :backfill snippet is for triggered badges, this should be a “check once per day” badge.

התגים לא מוקצים

תמיכה

riking (Kane York) 27 בינואר,‏ 2016,‏ 1:38am 15

This sounds like a badge that should only be awarded once per person anyways

נושא		תגובות	צפיות
Previewed Badges not Awarding Product Support badges	4	1235	4 בספטמבר,‏ 2015
Badge preview working, badge assignment not working Product Support	1	1003	25 בינואר,‏ 2016
[solved] Badges 'update daily' won't trigger Product Support	2	1620	25 בפברואר,‏ 2015
Badge grant fails if any throw exception Bug	3	1178	29 במרץ,‏ 2015
SQL Querying in Badges Data & reporting sql-triggered-badge	1	1122	4 בדצמבר,‏ 2015

התגים לא מוקצים

נושאים קשורים