Does this still work
Opened this issue · 5 comments
I'm testing this in Lambda, and it's reading the accounts and detecting the full accounts but when it says "Switching xxxx back to basic" it doesn't seem to do anything to the related account
@martinlee-awaze hey sorry, NR changed how their users management system works and I haven't had a chance to revisit this. The new system don't provide a last login field so we'd need to store this data somewhere to keep track of users full status.
Thanks for the update, it does seem to detect the relevant acccounts and can see last_access_at (see example below) it just seems to be the part where its trying to change the user_tier_id from 0 to 1 that's not working.
"last_access_at":1620978462
hmm, if your still using the old user management it should work. I don't really have a way of testing this anymore though
Not directly related to this issue but have you seen this?
Because user type is a billing factor, we have restrictions around how often a full user can be downgraded to a basic user: a full user can downgrade to a basic user a maximum of two times in a rolling 12-month period. If a full user has been changed to a basic user two times in that 12-month period, that user won't be able to return to being a basic user until the start of the next 12-month period.
what the heck. that most certainly wasn't on that page previously. check the way back machine
