I might be wrong, but it seems like changes in bounce.toml are not applied until Kumo is restarted. Is there a way to force Kumo to reload that file without a restart?
That’s after waiting out the cache lifespan?
Yeah, I made changes to the bounces.toml file about 3 hours ago
the bounce classifier doesn’t current support any form of reloading, seems like an oversight
but still seeing Uncategorized as bounce_classification
I’m kind of scared of restarting Kumo, pretty much everytime I do it after a couple of weeks of it being running, it takes 5 minutes and then gets killed with SIGKILL when by systemd, which means > 5 minutes of downtime. It wasn’t a problem before, but we’ve just onboarded a new customer who send OTPs pretty much 24/7 and I’ll have to schedule a down time and ask them to use a backup provider.