MultiWalk Rollover Change Log

Sep 2 2026

  • Only one Rollover Monitor now runs at a time. If a second monitor is opened, the second window reports that a monitor is already running and will not run itself.  The monitor that is already running is not affected.
  • Two monitors can no longer overwrite each other settings. Each monitor keeps its own copy of your symbol lists and saves them every cycle, so two running at once would each write over what the other had just saved. The single instance protection removes that at its source.
  • When the internal symbol list is repaired, the activity log now records the damaged entries it found instead of reporting the list as blank.

Aug 25 2026 Update 1 (released Aug 26 2026)

  • Opening the monitor was very slow if your Rollover activity log file was extremely large. It is now fast regardless of size. Previously the monitor read the log from the beginning while checking for symbol list restore information, which on a large log could hold up TradeStation for several minutes at startup, presenting a black screen.
  • The startup self-repair of the monitored symbol list now keeps multiple generations of the last known good list in a dedicated backup file and automatically chooses the best available restore source.
  • The symbol database update list is now repaired when it is incomplete, not only when it is blank.

Aug 25 2026

  • Symbols are no longer removed from your list when TradeStation reports a loading problem. The failure is logged and the symbol retries on the next cycle. Previously the monitor dropped the symbol, but that state is often only temporary and the removal did not always match the symbol correctly, which could leave the list in a state the monitor had trouble opening. Both the trigger and the removal have been corrected.
  • The monitor now repairs a damaged symbol list at startup, restoring it from the last known good list kept in your setup file or activity log. Lists are also checked before every save, so a bad list is not written to disk in the first place. If an edit on the Settings tab contains entries that cannot be valid symbols, the monitor tells you what it removed and what your list is now.
  • The monitor now recovers on its own from an error during a symbol data update. Previously such an error could leave it waiting on an update that had already stopped, so later checks were skipped until it was restarted.
  • Your symbol database is now repaired rather than rebuilt, and it is never removed. Previously, if the database could not be read, the monitor treated that as corruption and rebuilt it from your symbol lists, which lost the stored contract details that rollover detection compares against, so a rollover around that moment might not have been reported. Databases affected by an older upgrade issue are now recognised and repaired in place with your data kept. A database that truly cannot be read is set aside under a dated backup name rather than removed.
  • TradeStation fixed their grid bug in Update 94. The workaround that has been carried since Update 89, widened in the Jun 9 2026 patch to cover Updates 92 and 93, now switches itself off on Update 94 and later, and the symbol grid fills at full speed again.
  • New typo protection when adding a symbol. If the symbol is not in the TradeStation rollover schedule, the monitor asks whether you meant to add it. Symbols already in your list are never questioned, and the monitor never removes a symbol on its own.
  • Notification action arguments, including any email password, are no longer stored as readable text in the setup file. Please note this is obfuscation, not encryption. Existing settings are converted the first time they are saved; if you go back to an older version you will need to re-enter your notification arguments.
  • The installation program now verifies its own work and, if antivirus software has removed a file, writes a README.TXT naming the file and explaining how to restore it.

Jun 9 2026

  • Patched Apr 22 2026 release with workaround for TradeStation’s ongoing grid bug.

Apr 22 2026

  • Resolves the error “Cannot find DLL library file: MultiWalk Rollover.dll”. The Apr 21 release of MultiWalk created a conflict with a shared DLL. I reorganized the shared DLLs between MultiWalk and MultiWalk Rollover to avoid this happening in the future.

Mar 4 2026

  • Added TradeStation rollover date schedule. Rollover dates will be read from CSV file using data provided by TradeStation. This information is stored in the file MultiWalkRolloverSchedule.csv found in the rollover program folder. File has been updated to include TradeStation’s 2026 contract rollovers. The inclusion of these rollover dates, in addition to all the other rollover checks in the monitor, provides extra assurance that rollovers will not be missed.
  • Added workaround patch for TradeStation Update 89, 90 and 91 issues.
  • Installation has been streamlined using an installation program instead of ZIP file.
  • Bug fix: If a symbol was removed from the rollover list AND it failed to load (i.e., it does not exist in TradeStation), the symbol continued to try to load every time MultiWalk Rollover was run and display an error message in the activity window. In other words, there was no way to get rid of the symbol once it was in the database. This was originally by design as we always want to keep symbols updated even if they are not currently being tracked. But they should be removed from the database if TradeStation cannot load data for the symbol.

Sep 8 2025

  • Release has been updated with workaround patch code for TradeStation’s Update 89 and Update 90 bug that crashes the platform.
  • If the rollover monitor was installed on a new system, the database was not being created correctly and would result in the error:
  • Could not initialize symbol database. Error: Could not load symbol data from symbol database C:MultiWalkProgramRolloversMultiWalkRolloverSymbols.db
    Error: Could not create symbol query for database C:MultiWalkProgramRolloversMultiWalkRolloverSymbols.db.
    Error: SQLiteDatabase::CreateStatement | Error 1 (no such column: SymbolFuturesPrvContractExpDate)

Sep 5 2025

  • TradeStation is not always timely with updating their symbol data servers. See this article for an example. This means that TradeStation’s continuous symbol contracts can be out-of-date. Since we use this contract as the basis for rollovers, rollovers can be missed. This can result in fees when TradeStation closes any open contracts to avoid delivery of the commodity. The MultiWalk Rollover Monitor now has a new notification action to generate alerts when you are X days before the First Notice or Expiration Date. These alerts give us an early warning that we are getting close to the expiration of a contract, regardless of the status of TradeStation’s continuous symbol. Contracts must be rolled over before these dates!
  • Alerts are now consolidated within one popup window/email instead of one popup or email per symbol.
  • Contract expiration date alerts will occur once per day, even if the Rollover Monitor is run several times a day. This is to minimize excessive spamming of the popup windows or email notifications.
  • New alert message token: %alerttype%. Use this in your notification program arguments to distinguish between “Rollover” and “Expiration Date” messages. If you already have arguments defined, be sure to change them to use %alerttype% to make this distinction!
  • Days that are within X days of FND/expiration dates are highlighted in red in the displayed symbol table.

Jul 16 2025

  • Notification Action form fields were not being updated when the Test button was clicked.

Mar 18 2025

  • A user was getting periodic permission errors when MultiWalk wrote to the activity log file. This caused the monitor to halt with an error. It is not clear why this one user was getting these errors, but it should not have stopped the rollover monitor from running. Therefore, I changed the way that the monitor writes to the activity log file. If the write fails, an error message will be displayed, but the monitor will continue to function.
  • Rollover dates for some symbols, such as Eurex symbols @FDAX and @FDXM, were not being recognized.
  • Other minor cosmetic fixes.

Dec 12 2024

  • Added “Test” button for e-mail/external program notification action
  • Added rollover timer interval to settings
  • Added addition progress messages directly to log file (not log window)

Dec 9 2024

  • Added ability to send e-mails for rollover notifications using new feature “Notification Actions”
  • When a rollover occurs, notification actions can now include:
    • pop-up message box
    • execution of an external program, such as SwiftMail for e-mail rollover notifications
  • Settings now have their own screen tab
  • Main operations tab has been expanded to display more rollover symbols and activity log
  • Updated rollover title headers and made several other cosmetic changes

Dec 2 2024

  • Updated title headers

Nov 29 2024

  • Corrected license issue

Nov 21 2024

  • Rewrote to use new symbol database format introduced with MultiWalk Oct 2024 release. Many enhancements. Monitor now tracks previous and forward contract and days to contract expiration.

Aug 30 2024

  • The MultiWalk symbol file format changed in the MultiWalk Oct 2024 release, which “broke” the MultiWalk Rollver app that used MultiWalk releases before Oct 2024. This Rollover release is compatible with pre-Oct 2024 releases.

Nov 2023

  • Initial release