WpkgPipeClient Problems - only runs once?

[Nils Thiele]

Hey,
im using WPKG in combination with WPKG-GP now for a while and im very happy.
But i wanted a way for the user to execute WPKG while the system is running without a reboot, especially for mobile system that arent alway connected to the network at boot up time.

I searched arround and stumbled open the WpkgPileClient.exe which allows normal users to execute WPKG, looks like the perfect solution for me, especially since WPKG-GP is coded in python and i could just integrate the pipeclient code into my little application.

The app starts after the user logged in a resides in the system tray, the user can right click the icon to execute WPKG Sync, with appropriate Warnings that any application could force close and the system might reboot of course. While WPKG runs the user will be presented with a small progress bar using the percentage output of WPKG-GP.

Now on to my problem, this seems to only work once every few minutes, i couldnt determine the correct time yet.
If i execute the function runClient after it successfully worked it only outputs "Initializing Wpkg-GP software installation" and stops right after that.

I looked at the code but most stuff is currently beyond me. What is forced delay between runs and is there a way to determine the time left until the next possible execution?

Thanks for any help!

PS: At the moment its only possible to run the Client with "Execute" or "Cancel", would it be possible to add a option of a dryrun or query wpkg command in the future? This way i could inform the user of what will be happening to the system before wpkg is executed?
I dont want to mess with the wpkg-gp code on my own yet because i probably break more than i would accomplish :)
My alternative is to execute wpkg.js from the application itself in user mode, getting the necessary info from the wpkg-gp configuration out of the registry.

[Nils Thiele]

Sorry to push this but anyone has an idea what causes the problem i described?

I also have to correct myself, it doesnt only run once but after a successfull run it wont work for a while, this could be 2 minutes but i also experienced over 20 before this command successfully ran again.
This happens on Win 8.1 as well as win7 clients.