Several flows use record_change + a date-equality condition (e.g. end_date == daysFromNow(60)) which only fires if the record happens to be edited on that exact day — so they don't run unattended:
- contracts
renewal_alert (T-60/30/7), renewal_draft
- hr
document_expiring_soon
- procurement
po_overdue
- compliance
evidence_expiring / evidence_auto_expire
Ask (interim, doesn't need the platform): rewrite as type:'schedule' cron flows (project daily_ai_risk_assessment is the template) — daily run + range query + loop. Long-term a declarative time-relative trigger is framework#1874.
Follow-up from the 9-template optimization + 9.5.1 runtime-testing pass. Platform-level gaps are tracked separately in objectstack-ai/framework (#1867–#1877).
Several flows use
record_change+ a date-equality condition (e.g.end_date == daysFromNow(60)) which only fires if the record happens to be edited on that exact day — so they don't run unattended:renewal_alert(T-60/30/7),renewal_draftdocument_expiring_soonpo_overdueevidence_expiring/evidence_auto_expireAsk (interim, doesn't need the platform): rewrite as
type:'schedule'cron flows (project daily_ai_risk_assessmentis the template) — daily run + range query + loop. Long-term a declarative time-relative trigger is framework#1874.Follow-up from the 9-template optimization + 9.5.1 runtime-testing pass. Platform-level gaps are tracked separately in
objectstack-ai/framework(#1867–#1877).