Job assembler acting different in same flow
Posted: Thu Dec 21, 2023 11:20 am
I have multiple job assemblers in my flow, that use the same metadata of the job. I have job identifier and number of files specified, no complete condition.
In the first stage, the assembler sometimes assembles a job when it has fewer files than required (Metadata says 9, but job is assembled from 8 files) and processes it without errors like a regular job. Now when this job reaches the other assembler, it is finally sent to the error connection, because not enough files exist to assemble it.
One thing to note here, is the reason why one file is missing. Sometimes the file has duplicate information for creating a pdf, which means Switch creates the same PDF twice, overwriting the first one. Could this be the reason Switch thinks that a 8 file job is good to assemble? Although the question still remains, why two assemblers act differently.
In the first stage, the assembler sometimes assembles a job when it has fewer files than required (Metadata says 9, but job is assembled from 8 files) and processes it without errors like a regular job. Now when this job reaches the other assembler, it is finally sent to the error connection, because not enough files exist to assemble it.
One thing to note here, is the reason why one file is missing. Sometimes the file has duplicate information for creating a pdf, which means Switch creates the same PDF twice, overwriting the first one. Could this be the reason Switch thinks that a 8 file job is good to assemble? Although the question still remains, why two assemblers act differently.