[ERROR] The Surge Alert cron job has failed: (psycopg2.OperationalError) SSL connection has been closed unexpectedly
[SQL: INSERT INTO log (message, user_id, timestamp) VALUES (%(message)s, %(user_id)s, CURRENT_TIMESTAMP) RETURNING log.id]
[parameters: {'message': '[INFO] The Surge Alert (Latest) cron job has started.', 'user_id': 0}]
(Background on this error at: https://sqlalche.me/e/14/e3q8).
[via @JonathanGarro in Slack] "as with 99 percent of the surge alert issues, it comes down to bad surge desk processes. it looks like theyve changed the data type for the molnix_status field from string to boolean. the error you see above is an insert error because of this on the logging side (not the actual alert table insert), so it isn't a real big issue - we just lose the log update telling us that a new one was added."
[via @JonathanGarro in Slack] "as with 99 percent of the surge alert issues, it comes down to bad surge desk processes. it looks like theyve changed the data type for the
molnix_statusfield from string to boolean. the error you see above is an insert error because of this on the logging side (not the actual alert table insert), so it isn't a real big issue - we just lose the log update telling us that a new one was added."