Same result.

When I create a short-cut it will run.

Target: "C:\ExpressGenerator - Majors\EG_EURUSD\Step11_Run_ExpressGenerator.cmd"
Start in: "C:\ExpressGenerator - Majors\EG_EURUSD"

When I put the following in my test.cmd file it will not run:

start  "C:\ExpressGenerator - Majors\EG_EURUSD\Step11_Run_ExpressGenerator.cmd"

I am trying to get it to work when I have my test.cmd file located on my desktop.  Does your work from the desktop?

> I am trying to get it to work when I have my test.cmd

The easiest way to run Express Generator is to have your CMD file in its directory.

I have tried to run it from a different directory, but I have used Powershell or JavaScript scripts because it is possible to set the "current working directory" for the new process to the Express Generator's directory.

Absolutely, I do the same, but my starting .cmd file and the file I reference via start are both in the same C:\express-generator\ folder. And then I reference that file in my task scheduler.

In an attempt to make various generator configurations easier to deploy, I have made all settings in "gen.settings.ini" generic for all possible configurations, placed only the account and symbol settings in "pair.ini", and then placed all the remaining settings in "pair.cmd".

The idea was to have multiple versions of "pair.ini" in nested folders (e.g. data sources, time frames, and pair groups). In this way, I just needed to navigate to the appropriate folder and run a group.cmd that would run each of the individual .cmd files in that folder. This process could be repeated in the future without any changes to the settings.

Unfortunately, it seems from reading other posts that all .cmd files must be in the express-generator folder. Is that the case or do I have it wrong?

P.S. Have I understood the sequencing correctly?
1. "group.cmd" runs multiple "pair.cmd"
2. "pair.cmd" runs "node.js", "gen.js"
3. "gen.js" runs "gen.settings.ini"
4. "pair.cmd" runs "pair.ini"
5. "pair.cmd" takes precedence over "pair.ini"
6. "pair.ini" takes precedence over "gen.settings.ini"

I should add, I don't make any changes to the files under the \bin folder because they change with every update. I made a copy of gen.settings.ini and simply called it generate.ini and placed it one folder level up under C:\express-generator, and then edited it to have all my generic settings.

No, each variable you want to call later needs it's own unique number, hence this at the top of generate.cmd:

set symbol=%1
set period=%2
set minutes=%3

Then in the start command that references generate.cmd (AllPairs.cmd for example) you use the variables you already set placeholders for (1, 2, 3, etc.). In this case symbol, period, and minutes. Thus the command you see that starts generate.cmd and then has symbol, period, and minutes afterward, in that precise order, because those were the 1, 2, and 3 placeholders already defined in generate.cmd. For example:

START C:\express-generator\generate.cmd EURAUD H1 60
START C:\express-generator\generate.cmd EURCAD H4 120

You can use whatever variables you want, as long as they are in the correct order. You couldn't say generate.cmd H4 120 EURUSD for example because symbol=%1, period=%2, and minutes=%3, you'd have to arrange the variables in the correct sequence to match the placeholders you defined. You can define as many variables as you need in this manner, just use them in the correct sequence.

Check this post with this particular update:
https://forexsb.com/forum/post/75525/#p75525

It is probably because I have validate_then_generate = true in my generate.ini file, that way it will look at existing input files if they exist, and ignore them if they don't.

Some of the new --input-match features might interest you as well.

Aaron, I checked your previous script and noticed that you export the strategies as [SERVER]_[PERIOD] but import them only by %symbol% for validation. If you work with H1 only, it is not a problem, but it may be if you introduce other periods.

In your script:

REM Generate Strategies
node .\bin\gen.js ^
 --symbol %symbol% ^
 --period %period% ^
 --input ./collections/ ^
 --input-match %symbol% ^
 --output ./collections/[SYMBOL]_[PERIOD].json ^
...

You can use:

 --input-match %symbol% %period% ^

You will match both the symbol and the period in this case.

for aaronpriest ... I understand that in your setup the generic settings are placed in generate.ini, and the universal settings like symbol, time frame, mins etc. are generated with variables in generate.cmd, but how do you handle settings that are unique to a pair like swap long and swap short?