How does:"Wait _ min for all instances of the series&q

aflohr · Post by **aflohr** » Sat May 18, 2013 10:52 pm

i upgrade to pacsone 6.3.7. When i use Autoroute with the new
"Wait "x" minutes for all instances of the series to be received, and forward the entire series instead of individual images" feature the series are forwared after 23min even when i set "x" to 1 minute.
Can you explain who this feature works und what may cause the behavior ?

Andreas

Post by **pacsone** » Mon May 20, 2013 4:00 pm

Did you check the Submit Time, Start Time and Finish Time of that forwarding job for that particular series, and see if there was any Retry attempts? There could be many reasons for the delay, e.g., network congestion, server too busy with many other jobs, etc.

aflohr · Post by **aflohr** » Thu May 23, 2013 6:08 am

i did as you say and found out the following.

if there are more rules for different destinations from one source modality the wait times are added to the predecessor

Example:
Autosend konfigured as follows:
Roule1) MR1 sends to Workstation1 with Wait time 10min
Roule2) MR1 sends to Workstation2 with Wait time 2min
Roule3) MR1 sends to Workstation3 with Wait time 15min

MR1 sends at 10:00:00

WS1 recieve at 10:10:00 expected 10:10:00 (that is ok)
WS2 recieve at 10:12:00 expected 10:02:00 (wrong in my opinion)
WS3 recieve at 10:27:00 expected 10:15:00 (wrong in my opinion)

Is this a bug or a feature ?

Post by **pacsone** » Thu May 23, 2013 5:32 pm

We'll need to collect the facts before coming to any conclusions, e.g., can you find the automatic routing jobs to "WS2" and "WS3" and check the following information?

Submit Time - The time when the jobs were submitted
Start Time - The time when the jobs were processed
Finish Time - The time when the jobs were finished
Retries - The number of retries attempted to complete the job

If MR1 sent in the study at 10:00.00, then the Submit Time for the 2 routing jobs to WS2 and WS3 should be near that time, and the Start Time for the routing job to WS2 should be around 10:02 and 10:15 for the WS3 job. So if you see the Start Time was way off for those 2 jobs or the Retries count is not 0, then they seem to suggest the server was under heavy job load (many other routing jobs), or the network traffic was too heavy which resulted in the retry attempts.

aflohr · Post by **aflohr** » Thu May 30, 2013 6:50 am

i did this already with the live data. There are no retry attemps and the server was not heavy loaded.

The Submittime for WS1-3 is nearly the same, the start time is 10.02 for WS1, 10.12 for WS2, and 10.27 for WS3

So I change the wait time as followed

Roule1) MR1 sends to Workstation1 with Wait time 10min
Roule2) MR1 sends to Workstation2 with Wait time 6sec
Roule3) MR1 sends to Workstation3 with Wait time 6sec

Now the images to WS1-WS3 are send at nearly the same time (10 min after recieve). BUT i can not send the images faster to WS2+WS3 than the wait time for WS1.

May you can check this in your test enviroment.

Post by **pacsone** » Thu May 30, 2013 4:13 pm

This is confirmed to be a bug in PacsOne Server, where the amount of delay time may be miscalculated if multiple delayed-forward routing rules are defined.

If you could send an email to mailto:pacsone@pacsone.net and let us know the version and OS platform of the PacsOne Server you are running, we'll be able to send you a URL link to download the patched run-time executable (PacsOne.exe) for your version/OS from our website.