It seems like if I don't trigger an API call for a while, the system puts my login into some kind of hibernated status that shows the error "{ error: 402, msg: 'Email inactivated' }"
Once I log into the web UI, my API calls work again.
Is this a normal/expected/documented behavior? Is there a way to prevent it from happening other than setting up a Cron job to run an API call often enough for the system to keep my login from getting "inactivated"?
It seems like if I don't trigger an API call for a while, the system puts my login into some kind of hibernated status that shows the error "{ error: 402, msg: 'Email inactivated' }"
Once I log into the web UI, my API calls work again.
Is this a normal/expected/documented behavior? Is there a way to prevent it from happening other than setting up a Cron job to run an API call often enough for the system to keep my login from getting "inactivated"?