Hello All,
I've encountered this issue a few times now, but was never able to find a straight forward fix to directly my problem until today. I use these community pages a lot for troubleshooting so I thought I would post my problem and solution for the first time in the hopes it helps someone out. Alteryx is obviously aware of the issue because they have an official page about the error. However they only offer the solution of "open prior version, check autorecovered files, try .bak files" which just didn't cut it for me. (Error: "The Tool ID [id] Is not in the document" - Alteryx Community)
My issue was that whenever I clicked on my batch macro icon, the configuration would not load and Alteryx would generate this message (An Unhandled Exception occurred):
Upon right clicking the macro and selecting open, or upon trying to open the macro directly from File Explorer, the workflow would not load and I would receive this message (The Tool ID X is not in the document.)
What causes this error is deleting an input file from the macro that at any point was attached to a control parameter or other interface tool or was converted to a macro input (this is where the bug in the Alteryx code is I believe). When this happens, a blank question remains in the code for that tool (in my case tool 1), but since that tool has been deleted the question generates the error that the specific tool is not in the document. It is quite annoying that this error prevents you from opening the workflow entirely. I've encountered this issue in the past and ended up starting over after not getting anywhere troubleshooting.
The solution is to edit the macro via text file.
- Locate Macro Workflow in File Explorer
- Right Click
- Select Open With
- Select Notepad
- Ctrl+F "<Questions>"
- Find the Question pertaining to your missing Tool. Here is what mine looked like:
- Delete everything from the <Question> to the </Question> tag pertaining to your missing tool. For me it what is everything highlighted.
- Save Text File
- Close
For me at least that fixed the issue and I was able to open the macro again. I really hope Alteryx can fix this issue in a future update.
Hope this was helpful!
