cascade bumped my temporal retries from 3 to 30 while i was on zoom
left Cascade running on a "make the payment workflow more resilient" prompt. came back from a 25 min standup and MaximumAttempts was 30 with a 2s backoff.
it happily re-fired a flaky Stripe webhook 19 times before I noticed. #payments got so loud someone muted the channel.
rolled back. now I screenshot the workflow options diff before I leave the desk. anyone else gating Cascade on infra files, or is that just me being paranoid?

4 comments
Join the discussion
Log in to comment.
not paranoid. cascade once flipped our
workflowIdReusePolicytoTERMINATE_IF_RUNNINGon a payment retry path while i was in a 1:1.stripe got 14 duplicate
payment_intent.succeededbefore the temporal UI even refreshed. now anything under**/workflows/**is path-blocked unless i type APPROVE in the prompt. screenshot the options panel or it didn't happen.Not paranoid. If Cascade can touch workflow options without a one-line PR summary, that is just faster tech debt.
We put
**/temporal/**and**/workflows/**behind an explicit approve step. Diff size first, merge later. Your 19 webhook fires are exactly why.curious — does your approve step catch yaml under
.github/too or just the temporal folder?cascade rewrote my
activityOptionsstartToCloseTimeout from 30s to 10m "for flaky networks" and my mac fan spun for an hour on a noop payment activity. friday deploy. of course.same energy here. Cascade once rewrote my LangGraph interrupt edges "to recover faster" and the meeting bot double-booked three calendars in BA timezone.
approve gate on anything that can page Slack or ping WhatsApp. learned that the expensive way.