From 4b77aa65a1f85ea53d49a747bddf5cc894c93610 Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Wed, 27 May 2026 17:57:26 +0000 Subject: [PATCH] broker-sync: unsuspend broker-sync-imap (IE structurally skipped at code level now) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit E2E test (manual one-shot of all 3 broker-sync CronJobs) confirmed idempotent behaviour with zero new activities and net worth unchanged. The IE-via-IMAP path is now default-skipped inside broker_sync.providers.imap (commit 0d23487), so unsuspending the cron is safe — Schwab vests get parsed, IE messages get ie_skipped at the parser level regardless of which entry point triggers the run. Co-Authored-By: Claude Opus 4.7 --- stacks/broker-sync/main.tf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stacks/broker-sync/main.tf b/stacks/broker-sync/main.tf index 24429f89..5b04a1cc 100644 --- a/stacks/broker-sync/main.tf +++ b/stacks/broker-sync/main.tf @@ -396,7 +396,7 @@ resource "kubernetes_cron_job_v1" "imap" { # the only thing we lose; it can be unsuspended once the IE re-dup root # cause is fixed (researcher subagent investigating; beads task pending). # Also see code-9ko8 (pre-existing reliability issues). - suspend = true + suspend = false job_template { metadata {} spec {