Braina "file not found" and indexing issues

[universalsoldier]

Hello support and fellow braina operators,

I have a two part issue that I am sure is either already being experienced by some or will help others just by the discussion on the topic.
So first, my braina is working fine for the most part, except what I am writing in for, and on the latest version. (I think 1.42? But I am not sure where to find that as there is not a usual help > about button to check).
The part that is not working, is a custom command and a new file I just wrote to automate a "pre-shutdown" procedure that I came up with to decrease the chances that windows 10 hangs on restart (which, my machine likes to do if I just shut it down without closing about 8 running programs first).
So put simpler, custom command is a .bat file and my command "shutdown" simply runs "open file shutdown.bat" so I can walk away from the machine or whatever.
The problem is, braina thinks about it and then dies with "No file or folder named "SHUTDOWN.BAT" was found.
I'm aware of brain's indexing and the need for it to know about files in order to run; in the past it seemed like it learned as you created files? I'm not sure if that changed or was just me imagining things, but it seemed like I could use files immediately as soon as I created them whether it be a new program that was installed, and creating a custom command to the .exe or a batchfile or powershell script, etc.
So I checked brainas settings and first found that under Tools>Settings>Other that "automatic file indexing preference" was set to weekly. That also made me remember the initial issue I had with indexing, reinstalling braina this last time after a new computer migration. The "automatic file indexing preference" we set to weekly, but then I'm not sure how it ever worked for programs or files I just created ever worked, so I'm scratching my head here.
This brings me to the second part of my problem.
When I reinstalled braina most recently, which may have been after a computer migration, or it may have been for a braina update, I remember it finishing and starting its file indexing process. To my horror, I saw the indexing process start going through each folder and causing onedrive to download each file from the cloud to my local machine! As we have now moved to "the new way" of doing things in personal computing; the default for our files and folders, assuming one has a normal onedrive / microsoft account integration, is for your desktop and everything in your \documents folders to all be stored in your onedrive / the cloud, and only leave a shortcut on your machine. If you want to open one of the files, you have to wait a moment for it to be downloaded before you can open it. Or, you can adjust the settings of onedrive to "always keep on disk" and it will download everything after a new install. It makes computer migrations so much easier than before, and I really like the default cloud storage, as theres plenty of files I never use but would like to have access to. It appears though, that "indexing" to braina, also means that it needs to "see" or "open" the file partially? Therefore causing a download of the file to occur. I stepped in and interfered with the indexing process braina was doing and stopped it, so it wouldn't download any more files.
My thoughts were, damn, okay well it won't be indexing the files,  I won't be able to use braina to search for files or play music, but I have never really used braina for either, so to me that was not a big deal. I thought I could still use "open" commands with full path specified, especially in custom commands, to get around the lack of indexing limitation. Since its been a long while since I did a custom command, it appears that is not the case.
So several things come to mind.
1) Even though brainas "automatic file indexing preference" was set to "weekly", I don't think it was doing that, because my files were all still in the cloud, and not suddenly all downloaded one day.
2) Specifying full path in the "open file" custom command (or even typing it into brainas input field) doesn't work like I thought it would. I've tried with and without quotes, so its not a path / spacing issue.
3) Older files that have been around a while that I have created on the machine can be opened, but ones recently created cannot. So maybe the indexing is working, just only weekly before since that is what I had it set to? But why it would now ignore cloud files / shortcuts is beyond me.
Any help / feedback / suggestions would be greatly appreciated.
Thanks,
Adam

[saurav]

Just use "open" command and not "open file" command. Please specify complete path to SHUTDOWN.BAT and it should work.

open "<path to shutdown.bat>"

PS: open file command searches for file in the index and then opens it if it is found while open command just opens the specified file path. Open file command will not work if Indexing is disabled. Open command will work even if indexing is disabled.

[universalsoldier]

Just use "open" command and not "open file" command. Please specify complete path to SHUTDOWN.BAT and it should work.

open "<path to shutdown.bat>"

PS: open file command searches for file in the index and then opens it if it is found while open command just opens the specified file path. Open file command will not work if Indexing is disabled. Open command will work even if indexing is disabled.

Thank you so much for your response, and sorry for the literal months it took me to respond; my communication preferences were set to email like I thought, but apparently the how often setting was set to "never"!
I thought I recalled using the open "c:\path" before, but it hadn't worked when I tried it. Probably missed the double quotes.
One thing I've always wished about Braina is a good list of all the commands and syntax somewhere in the help file or online.
You've resolved my biggest and most vexing issue for me. Any idea on how to get braina to update the file indexing without dragging through the computer with a net, pulling all the remote / cloud stored folders down?
Thanks a million!!!!!