-
Notifications
You must be signed in to change notification settings - Fork 93
Group updates failing to push to Discourse #1067
Comments
I should add that it APPEARS to work if a user is in a group that has already sync'd with Discourse but I've noticed this after a new corporation joined the alliance and their corporation group has not been pushed at all to Discourse. Even adding myself to the group in auth does not trigger it, just gets caught in an endless loop of trying and failing to update. |
Oh boy. Discourse rate limits. I thought I'd never have to deal with this. You can allegedly disable API rate limiting by setting This seems like another obvious candidate to employ celery bootsteps like I'd looked into for #1064 - I'll keep digging. |
Maybe related, maybe not, but in the Notifications in auth I've been getting these repeatedly. Perhaps it's just repeatedly failing to update groups and keeps trying for some reason? We only have 110-120 users on Discourse at the moment so it's hard to imagine it's the API limit due to normal usage.
I'll try tweaking the API and see how it goes. I've noticed groups either don't or are really slow to update now. For example when someone joins corp or joins a group, it's a 50/50 shot of it making the update on Discourse. |
My worker.log file is filling up with errors regarding group updates failing to push to Discourse. Not sure if something changed with a Discourse update or what but all of my information in the configs are correct. Wondering if anyone else is running into this or where I can look to troubleshoot this further.
Before and after this particular error is just logs of it trying to push and fail, stating it will retry in a certain amount of time before it just cancels the task with this error.
The text was updated successfully, but these errors were encountered: