KnightWare wrote
This does use an external SQL Table.
This is relevant and significant information that was omitted from the original question. Hence why an example was requested. Also the example you've sent isn't something I can run locally as there is no sample data and I don't know what the shape of the data that you are trying to retrieve is.
As Jaymer said it is highly likely that the External SQL table is the problem.
Build a small BSV that uses internal data then create the two processes and use it against your local data. That will triage the issue down to the external data table. The likelihood is that the issue relates to the way AIM holds external data in context. If you have not created some persistent BOs in AIM to hold the data you are likely to encounter an issue. Bear in mind the FIND IN BATCH will also create problems when you are using external data that you are updating, your FIND would need to use an attribute that you have updated otherwise you risk returning the same instance of the BO repeatedly as AIM won't be holding it in context if you batch by 1.
Like Jaymer said you don't need to use START PROCESS to call another process, but if you do then it obviously makes it clear that you are calling a process when you return to it later.
