Improve error handling with #ipregistry API for unexpected cases

Stop retrying failed image generation prediction and instead return error message to chat #wip

random sample guidance scale on 10% of queries too to figure out best #photoai

Fix -Infinity% alert delta when previous period had zero alerts #sitewatcher

create a error notification system for user api keys #drippi [Automated via open.jaen]

create a error notification system for user api keys #drippi [Automated via open.jaen]

create a error notification system for user api keys #drippi [Automated via open.jaen]

improve #filepond promise rejection

notify admins of suspicious comments (e.g. including certain keywords, or high volume of comments in short time, etc) #betalist

Config monitoring system to check Domain Drop every 20 seconds... Can I beat the catchers yet again? #mcpizzalife

generic error handler / notification system #mindnite

Improve error responses #branddev

setting up usage warning emails once active subscriber hits a certain % of usage. That way, we can support them better on a higher plan, or ask them to reduce their certificates count. Currently using: Supabase Edge functions, Resend API, Supabase pg_cron, pg_net #scoredetect

add error message if training fails #photoai

Added retries and backoff to all message analysis jobs in Watchdog so I can stop getting paged for intermittent 5xx errors #watchdog

wipe data from db on X amount of failed requests? #pinlocker

Better error handling in #fashn API

much better error handling #httpscop

Setup Sentry alert #devjob

Think about new design for error handling for the X bot (because X goes down a lot and rate limits at a random interval, this should make things more reliable over the long term): Think I'm going to make each browser function fail after 10s max (library I'm using currently deadlocks if the element doesn't exist on the page since it retries indefinitely) which would then trigger a refresh after a delay #watchdog !private