A user was unexpectedly deactivated after years of activity, despite regular API usage. carlokok initially mistook the status as “staged” but clarified it was deactivation. jomaxro suggested the likely cause: automatic deactivation of inactive admin accounts after one year of no site login. carlokok confirmed the user was an API-only admin and disabled the auto-deactivation feature. hosna reported a similar issue affecting API-based signups and urgently requested disabling the behavior. carlokok and dax pointed to the site setting invalidate inactive admin email after days, which defaults to 365 days — the root cause of the automatic deactivation. Users are advised to adjust this setting if API-only admin accounts must remain active without login activity.
Trying to follow, but this is confusing me:
Are you sure you mean staged? Or do you mean not activated?
I did mess up terminology yes. The user got de-activated, not staged. For what it’s worth, it hasn’t happened again (yet?)
Without knowing some additional data about the user, my best guess is that they hadn’t been seen on the site for a year, and are an admin, and as such were automatically deactivated. Does that sound right?
Yep! Only problem is that their api key is used a LOT, just never logged in. That said, thanks, I’ve disabled this option for now.
happend to me this morning. how to disable such behavior?
I need this to be disabled fast. cause ppl signup in my application by discourse api. and the api user is inactive and only used for this.
There’s an option to disable this. Search for inactive.
The site setting is called invalidate inactive admin email after days and by default is set to 365 days.
