Message step: Whichever comes first? Clicking OK still waits for timer to run out.
Gary Semel
I have a package with a Message as the first step. The message is configured to Wait for User to Click OK and 120 seconds. When I deploy the package to my pc (also running the PDQ Deploy UI), I see the popup, and I click OK after about 10 seconds, but the deployment status grid in the UI shows the message step is still processing for the full duration of the timer. Step 2 doesn't start until about 130 seconds after the deployment started.
Am I wrong expecting when the user clicks OK the step should end and continue to the next step?
Thanks!
0
Comments
Are you using just a msg command? Did you write this step as Powershell? It sounds like your logic isn't quite correct in that the message is displayed and interacted with but the script is over because 120 seconds isn't up.
You need to create logic that say "If message is acknowledged before 120 seconds, exit, else wait the full timer amount and exit."
Thanks for the reply, Stephen. Here's a link to some screenshots that may clarify what I'm seeing.
http://imgur.com/a/tvr70
Image 1: The Message step definition. I changed it to 60 seconds.
Image 2: The running deployment status at a few seconds in, showing it's on Step 1 and the msg popup.
Image 3: After I clicked the popup Ok button at around the 20 second mark, but it's still on Step 1 50 seconds into the deployment. I had to grab this screenshot before the 60 second mark, when it would go to Step 2.
Image 4: Finally moved on to Step 2 at the 65 second mark, 45 seconds after it should have started Step 2 when I clicked the Ok button.
Thanks for the help.
Oh, ok. You're using the actual message Step in PDQ. Makes much more sense now! Hmm. Which version are you on? Latest? You could have potentially found a bug.
11 Release 2 Enterprise Mode (via a trial key, going to buy a Pro license before the trial ends).
Thanks!