Which dedupe strategy fits Deta Space scheduled actions for low-noise alerts?
I'm building a Deta Space app that runs a scheduled action (cron trigger declared in the Spacefile) to check a condition — for example, stale data or a quota threshold — and send a notification through a third-party channel like a Slack webhook or email. Since Space has no built-in alerting or notification subsystem, all of this logic lives in my own code. T
detaspace