rtrouton

It appears that it was. Please see below: ``` JamfPackageUploader: No value supplied for pkg_name, setting default value of: JamfPackageUploader: No value supplied for pkg_info, setting default value of: JamfPackageUploader:...

Assuming that is a timing issue, is there some way I can force a pause between running the JamfPackageUploader and JamfPolicyUploader processors? I’m on a Jamf Cloud Premium instance and...

Ah, just thought of a way to force a step in between. I can move the category upload for the policy category from before the package upload to after the...

As far as I can tell, this timing issue doesn’t happen with JSSImporter. I’m actually running Jamf Upload side by side with JSSImporter, where I have one AutoPkg instance with...

The `/tmp/jamf_upload/curl_cookies_from_jamf_upload.txt` file doesn't appear to exist on my AutoPkg instance running Jamf Upload. I have the following files in `/tmp/jamf_upload` (see attached): - curl_headers_from_jamf_upload.txt - curl_output_from_jamf_upload.txt [curl_headers_from_jamf_upload.txt](https://github.com/grahampugh/jamf-upload/files/8233353/curl_headers_from_jamf_upload.txt) [curl_output_from_jamf_upload.txt](https://github.com/grahampugh/jamf-upload/files/8233354/curl_output_from_jamf_upload.txt)

I've updated my recipes to move the category upload for the policy category from before the package upload to after the package upload. We'll see if that makes a difference...

So far, it looks like moving the policy category upload to after the package upload has addressed the issue. I haven’t seen the issue re-appear after four days.

Never mind, it just happened.

Would it be possible to add a “wait” Input argument to the processor? Allow the value to be an arbitrary time in seconds and set the default to zero.

That would allow folks with this problem to set their recipe to however many seconds are generally needed (in case the cookie isn’t there) for the package to register before...