Currently, if some error happens to the DB, the entire process (Global Controllers + Local Controllers) get shut down, which is both annoying to operate with and annoying to debug with.
When such an error comes, make a log of it instead, and keep the program running. The DB does not have to update in that case, but just send a log explaining that.
This is mainly a logging + try/except addition.
Currently, if some error happens to the DB, the entire process (Global Controllers + Local Controllers) get shut down, which is both annoying to operate with and annoying to debug with.
When such an error comes, make a log of it instead, and keep the program running. The DB does not have to update in that case, but just send a log explaining that.
This is mainly a logging + try/except addition.