Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
TypeScript agentaiai-agentsall-in-onecrmcrm-systememaillinearmcpmessagingnotesnotionofficerustslackslack-alternativestartupstartup-toolstypescriptworkspace
notification_retention_handler
What it is
Internal scheduled notification cleanup. The owning notification domain enforces 30-day retention and bounded transactions; this binary only composes it for Lambda.
Start here
src/main.rs: one-connection pool, retained telemetry provider, post-invocation flush. Close handler spans before flushing; never shut down warm providers.src/handler.rs: explicit dry-run default, invocation deadline and request ID.infra/stacks/notification-service/retention.ts: configurable schedule, pinned Datadog extension, scoped key access and nonduplicated log forwarding.
Checks
cargo test -p notification_retention_handler(SQLX_OFFLINEunset).cargo test -p notification -p macro_entrypointfor policy and flush behavior.- From
infra/:bun test stacks/notification-service/retention.test.ts.
Gotchas
{}is read-only;{"dry_run":false}permanently deletes hosted data.- Telemetry failure preserves the operation result; it must not trigger a retry of already-committed deletion. Flush time comes from reserved handler headroom.
- Unit tests cannot prove the deployed extension exported traces. Verify an explicitly approved dry run in Datadog before production cleanup.
- Dev and prod stack configs enable scheduled deletion every hour; deployment still needs explicit approval and the runbook's rollout checks.
Related
docs/runbooks/notification-retention.md.agents/rules/observability.md