Flow submitting a single job multiple times??

Sort:
You are not authorized to post a reply.
Author
Messages
LauraPat
Veteran Member
Posts: 50
Veteran Member

    I have a fairly simple flow.  A user places a file in a specific location - a File/Channel in Rich Client detects the file, passes it to the LSF server and then a Lawson job is kicked off (via webrun node) to process the file.  It's a CSV file with vendor numbers - the batch program they are being passed to is doing an invoked of AP10 to inactivate the vendors.

    I ran it with 10 records, 100 records and 1000 records and it worked perfectly.  I then decided to drop 50,000 records in the.  The job was submitted via the webrun node - after 15 minutes (exactly - right to the second) the job was submitted again and 15 minutes later it was submitted a 3rd time.  The 2nd and 3rd job went into waiting because the program being executed is non-concurrent.  As soon as the first job completed successfully - I realized a second job was running and that's when I saw the multiple jobs so I killed them.

    I have NO idea why this is happening.  Neither does Infor support so far.  The flow in total ran about 44 minutes from start to finish (including the job).  I think if it had run longer - I'll be a 4th iteration of the job would have been submitted (exactly 15 minutes after the 3rd iteration).

    Anyone ever seen this?  ANY ideas at all on what could be causing it???

    Thanks in advance.  We are V10 On premise.

     

    John Henley
    Senior Member
    Posts: 3348
    Senior Member
      I’m guessing your interval on the ipa channel is 15 minutes? And your flow takes longer than 15 minutes to run so the channel is seeing the file over and over as a new file.
      Thanks for using the LawsonGuru.com forums!
      John
      Karen Sheridan
      Veteran Member
      Posts: 141
      Veteran Member

        We had this happening on a long running PR530 (time record upload) job.  We changed two things.  One, we had the old cgi in the webrun.  Two, I added a waiting loop to wait for the PR530 job to finish before moving on.  It could be the file channel kicking it off again as John said.  But, the file channel moves the file to a different directory that its not monitoring, unless you don't have it set-up that way.

        Karen

        You are not authorized to post a reply.