Automating Futures Robot Start and Stop Schedules
Summary
The post describes a time-based controller for starting and stopping automated domestic futures trading robots. It checks the current time and weekday, uses a status flag to avoid repeated starts, and calls platform functions to restart or stop two named robots. The author reports that the system can run normally for a day but sometimes fails, showing a connection-reset error during an API request.
The excerpt illustrates operational scheduling and a possible network or service interruption during remote control calls. It does not provide a confirmed diagnosis or a robust recovery design. Its time-window and weekday conditions also deserve careful review, since logical grouping can affect when a stop condition fires. The post gives no evidence about trading performance or whether the automation reliably handles holidays, retries, or failed API calls.
Key ideas
- The controller uses current time, weekday, and a status flag to schedule robot restarts and stops.
- API calls can fail with a connection-reset error even after periods of normal operation.
- The error is reported but not diagnosed, so its underlying cause remains uncertain.
- Time and weekday conditions should be checked for intended behavior, including operator grouping.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.