Another potential workaround I considered is to use different instances of the program
- One to write the selections of any given strategy to a txt file, and tag each with the relevant strategy using the imported_1 etc operator
- Another with all selections disabled by default which executes the bets and manages the staking, by using different triggers per strategy that is each conditional upon the presence of a specific imported_ value.
On which point, I believe there may be a slight bug in the Import Selections For Auto Trading function. I'm using a trigger to write a long list of selections to the .txt file that another instance of the program is importing from. I'm then using Dropbox to manually delete selections that I don't want to bet on, so that this is sync'd with the machine running MFP.
Quite often, even though the trigger is set to refresh the file every 5 seconds, it's not picking up the changes - particularly on Day 2+. The manual refresh button has no effect either. However, if I manually re-import the file by re-defining the filepath (to the same file) then the selections are imported no problem