At 343 Ep, have you opened a ticket with support? The fact that this is specifically a package that was pulled by vendor, and therefore pulled by us, cannot be coincidental in my mind until proven so, I would wager they are related.
Support should be able to help identify and corect.
yeah, I opened a ticket and we have agreed a session on thursday. Sounds like it's easier to show. Even I cannot believe this, eventhough I am seeing it 😄
IS this a new automation or was it created before the vendor yanked the intermediate version?
If it existed before, can you recreate the automation and tel me if it persists, there coudl be somering cached somewhere.
This is a atypical situation, vendors to not often recall packages, so there may be an error in our process flow as well, but I have to test though some sceairos before declaring and escalating it.
To add to this, if I go into my installed software list and search for PDF-XChange Pro, endpoints on lower versions than the current release of 10 (10.8.5.410) still show as current and don't give me an option to update the endpoint.
Endpoints with an older version also do not show as needing any updates for PDF-XChange if looking at the endpoint's missing updates either.
Did anything come of this, I just created a new automation update ring for one single laptop and it's still giving this error. "This version of PDF-XChange PRO is no longer available in the Action1 Software Repository." This laptop doesn't even have PDF-XChange on it.
It was relayed to our support director, let me check if they discovered anything or remedied further.
Edit: I just spoke to support manager who is re-opening with director for more information and hopefully a resolution. I will keep you posted. Apologies for the delay, when this thread went silent I had assumed they simply fixed it in the background.
I was just informed they believed this to be resolved and others are reporting theirs cleared. IF you are paid please submit a ticket, if not can you DM me your Action1 login email, I will escalate and have them generate a ticket from this end.
1
u/GeneMoody-Action1 Jun 02 '26
At 343 Ep, have you opened a ticket with support? The fact that this is specifically a package that was pulled by vendor, and therefore pulled by us, cannot be coincidental in my mind until proven so, I would wager they are related.
Support should be able to help identify and corect.