Proposed feature
Currently, the limits for token consumption only work within the running process. If the app crashes, monitoring will start again at 0. If the limit is hit, the error message should display a better fitting error than "an error occured".
Move token consumption in a settings table that is persisted.
Proposed feature
Currently, the limits for token consumption only work within the running process. If the app crashes, monitoring will start again at 0. If the limit is hit, the error message should display a better fitting error than "an error occured".
Move token consumption in a settings table that is persisted.