Index was outside the bounds of the array.
I was wondering if someone could help me with the root cause to the above error. The model is working fine locally...meaning I can import the data in Monarch and export with no issues. Once I bring the project and model into Automator and set up a process to monitor for the input file, I am getting this error when the job attempts to run. The first time this happened to me I searched the internet and didn't find any answers so I proceeded to create a new model and rebuild everything. In that scenario this worked and that process is still working until this day.
This time (working with the same data, just a different model to extract some additional data from it) I ran into the same issue and proceeded to rebuild everything but no success this time. I was thinking it had something to do with a calculation I'm doing or something to do with the data, but my other models are working just fine on this data set.
Any help would be appreciated. I feel as though I've exhausted any idea I might have to find the root cause of this.
I'm running monarch 13.5 and Automator 12.5. I have about 50 processes that are running just fine.
Thank you in advance.
Answers
-
My further investigation indicates this has something to do with the "Start Region" and/or "End Region" templates I'm using to isolate the data I'm looking for based on some header information. Once I deleted these templates the job was able to run successfully; however I'm now working on getting rid of some "extra" data that is being picked up because I'm no longer using this function.
0 -
Altair Forum User said:
My further investigation indicates this has something to do with the "Start Region" and/or "End Region" templates I'm using to isolate the data I'm looking for based on some header information. Once I deleted these templates the job was able to run successfully; however I'm now working on getting rid of some "extra" data that is being picked up because I'm no longer using this function.
It looks like you pinned down your problem. I believe region templates (start/end) were a new feature in v13 so if you try to run a v13 model against v12 Automator, I would not be surprised by some weird behavior being thrown by Automator.
0 -
Altair Forum User said:
It looks like you pinned down your problem. I believe region templates (start/end) were a new feature in v13 so if you try to run a v13 model against v12 Automator, I would not be surprised by some weird behavior being thrown by Automator.
That makes sense and I agree... to work around this I was able to extract the report name from the header of the report and append to each line of detail. Then I was simply able to filter on this data element to return the records I was looking for without using the Start/End region function. Runs a little slower now though since I cannot tell it to ignore a great portion of the source data. but it will get the job done until we get our Automator version up to date.
Thanks for your input....much appreciated... Hope this thread helps someone should they run into a similar scenario.
0
Altair Employee