Calendar API into EA for auto-disable
Posted: Tue Sep 15, 2026 12:09 am
Calendar API into an EA for auto-disable -- practical notes.
I want algos flat around tier-1 events without relying on me remembering. Calendar inject / API disable flags help -- with caveats: clock sync, event importance mapping to your symbols, and fail-safe if the API dies (fail closed: disable trading).
Design
Blackout minutes configurable per event class. Log every disable/enable. Do not auto-reenable into a still-wide spread; add a spread gate after the window.
Automation of discipline beats heroic overnight monitoring. Test on demo during a known CPI week before trusting live.
What fail-safes do you use when the calendar feed glitches?
Keep a manual override you can hit without redeploying code. APIs fail on the day you need them. A big red disable -- tested -- is part of the system. Automation should reduce babysitting, not create a new single point of failure you ignore.
I am interested in how others on this desk handle the same problem without turning it into folklore. Concrete rules and log fields beat slogans. If you have a version of "Calendar API into an EA for auto-disable" that survived contact with live sessions, what does the rule look like on a sticky note -- and what did you try that failed?
I want algos flat around tier-1 events without relying on me remembering. Calendar inject / API disable flags help -- with caveats: clock sync, event importance mapping to your symbols, and fail-safe if the API dies (fail closed: disable trading).
Design
Blackout minutes configurable per event class. Log every disable/enable. Do not auto-reenable into a still-wide spread; add a spread gate after the window.
Automation of discipline beats heroic overnight monitoring. Test on demo during a known CPI week before trusting live.
What fail-safes do you use when the calendar feed glitches?
Keep a manual override you can hit without redeploying code. APIs fail on the day you need them. A big red disable -- tested -- is part of the system. Automation should reduce babysitting, not create a new single point of failure you ignore.
I am interested in how others on this desk handle the same problem without turning it into folklore. Concrete rules and log fields beat slogans. If you have a version of "Calendar API into an EA for auto-disable" that survived contact with live sessions, what does the rule look like on a sticky note -- and what did you try that failed?