Hi all! I have a list of emails in a CSV file that I am awarding a badge to. I expected a group to not be matched on our forum (I am using the list of all attendees of an event, and not all of them have a forum account). It seemed to work, many were matched just fine – but I noticed that someone who should have gotten one had not. I tested it again with just his email address in a CSV, and it still popped up as not matching an existing user. [IMG_3736] I double checked and his primary email on the forum is indeed the same as in the CSV. Any ideas for what’s happening here? :thinking: It’s a list of several thousand people, so I can’t double check everything manually, unfortunately.

[image] Mia: I tested it again with just his email address in a CSV, and it still popped up as not matching an existing user. Try the username instead of email.

I could do that for this one example, but since I have a list of thousands of emails and not usernames, it wouldn’t scale to everyone else.

I don’t think so – I tried cleaning up the data and now I’m getting a 502 error :sweat_smile:

You can try check the logs? I’m not sure if I’m well suited to help you out with this, but I’ll try.:person_shrugging:

These are the errors it has at that time… a new-to-me problem to solve :lolsob: [Screen Shot 2024-05-30 at 4.59.53 PM] I’m about to log off for the day, but I found this thread around MaxMindDB to start trying to debug this tomorrow :person_shrugging:

Also, thank you for helping! I didn’t know where the logs were, so it’s a good thing to learn!

These warnings are unrelated to your issue. Everyone who did not configure a MaxMind licence key sees them. Since people are wasting time investigating these warnings, when they face other issues, I wanted to mute them. However, my commit was reverted, since it broke some other CI tests and dev environments. Needs to be redone in another way. Regarding your issue, here are the relevant code blocks: discourse/app/controllers/admin/badges_controller.rb at main · discourse/discourse · GitHub discourse/app/services/badge_granter.rb at main · discourse/discourse · GitHub I do not see any obvious bug, but I am also no Ruby programmer. I tested it on our instance with a single and two email addresses in a simple comma-separated CSV, and it did work. It did also work, regardless whether I use LF or CRLF file endings, just to rule out some common file parser issues. How do you create the CSV file, and does it look fine when you open it in a simple text editor, like notepad, nano, vi, whatever?

Awesome, thanks for your help. That’s what I was thinking about the MaxMind warning, but I only had time to read briefly before I logged off yesterday. The CSV file is generated from Salesforce and it has one email address on each line, no commas or spaces. When I paste it into a basic text editor, it looks totally fine; no extra characters or anything. I also tried with a new CSV with a single email address and had the same error.

[image] Mia: The CSV file is generated from Salesforce and it has one email address on each line, no commas or spaces Strictly seen, it is no CSV then, which stands for “comma-separated values” :wink:. But I know the file extension is widely used also with other separators, and more importantly, line breaks are common as data set separator, so one email per line should work, and … it does work here. Actually, I did a wrong test yesterday, since I added my valid email first and the invalid 2nd. I thought it just skips non-existing emails silently, but actually it parses the first entry of each line only, hence does not allow multiple email addresses on each line. The code actually makes this quite clear: line = CSV.parse_line(line).first&.strip And then it adds the whole line value as one email or username entry to match. When I add multiple emails into one line each, mixing valid and invalid ones, it shows the correct number of successfully applied batches, and lists all emails which could not be matched. Again tested with Windows and UNIX line endings: [Die Grafik zeigt ein Tool zur Vergabe von Badges an Benutzer durch Hochladen einer CSV-Datei mit Benutzer-E-Mails oder -Namen. Es gibt die Option, Badges von vorherigen Besitzern zu entfernen. Die CSV-Datei wurde erfolgreich hochgeladen und 2 Benutzer erhalten das Badge. Zwei Einträge in der CSV-Datei konnten jedoch nicht mit existierenden Benutzern abgeglichen werden und erhalten daher kein . (Captioned by AI)] Multi-line or multi-value is however anyway not your issue, if it fails on the very first email despite it is correct :thinking:. Not sure how to easily debug without rebuilding the Discourse instance. You use the official Docker image installer? EDIT: Lol, the image caption was added by some KI, in German language, at least here in my German locale browser. Pretty detailed, and very correct :smile:.

Bulk badge grant not working?

Product Support

Noah May 30, 2024, 8:21pm 4

Does your csv file has any invisible characters or artifacts?

Topic		Replies	Views
Assign badge to multiple users at once Product Support badges	10	714	March 3, 2024
Bulk Award a badge to a set of users Announcements badges , new-feature	28	6646	March 31, 2025
Award badge to a set of users and mention topic "reason" Feature	3	627	October 25, 2025
Bulk grant badge based on email Product Support badges	1	314	September 29, 2023
Badge Granting in bulk or for a group of users Feature	5	3315	January 20, 2020

Bulk badge grant not working?

Related topics