Sure – it’s completely Docker, on Digital Ocean. I followed that excellent guide to the T.
Sure, I just changed that setting from default 3 to 99999. No different, still getting the 500 error.
Tried that, no difference. Note that I still get the 500 error with ONE “bad” account, through Insomnia. So at this point, it’s like that one account is poisoned, and even if I just make the one “create message” API call with it (none before or after), I still get the 500 error. But yes, my import script is getting the 500 also 
Yes, I’m an experienced coder but don’t know RoR/Ruby at all, so I can’t really use the off-the-shelf options that y’all provide, though I recognize they are likely superior to me manually walking my existing forums and creating users, etc on the fly via API. Thus my marketplace post… I would love to get this all working for myself but I also have a hard deadline
Totally get it, and I appreciate your attention to this.
So here’s something that I can offer which might help a lot: since it’s an off-the-shelf installation, and I haven’t done much of any customizing, AND the bug is easily reproducible without my code (just use Insomnia) AND I haven’t launched the forums, I could pass you the root login for the Digital Ocean instance, my API key etc., and I have no problem with you mucking around in there. My Discourse forums are currently a ton of empty categories and a few other special intro messages we’ve set up, but it’s basically empty and no real users are in there yet (just admins). So it would be fine if you want to test things, create/erase topics and messages, etc.
This would definitely be the fastest way to see the bug first-hand for yourself. And then since you would be in there as root, you can also muck with whatever low-level Discourse things you want, to find out why this is happening.
E