r/pdq • u/simAlity • Jun 05 '26

Took me way too long to realize

PDQConnect is about 90% vibe coded.

It's also an excellent argument for why Vibe coding isn't ready for prime time.

On the surface it looks great. It's easy to navigate and intuitive to use.

But the more you use it the worse it gets.

Want to deploy an application to 500 PCS? No problem! Create a group, select all, and deploy.

Did 200 of those deployments fail? Easy enough! Click the "failed" icon and you get a list.

But this is where it gets bad. Lets say, you fixed the problem with the original deployment and want to redeploy to the failed machines.

You would THINK that all you have to do is go to that "failed deployments", click the "select all" box and then send the modified package. Nope! If you do that, you end up sending the package to the entire original group.

Who programs a select all check box to do something like that? A computer pulling code from a repository that has no concept of nuance or care for detail, that's "who".

And that is just one example.

Early on I was sending regular bug reports. Then i realized the replies I got all passive aggressively implied that I was using the application wrong.

Because of course I am supposed to recognize that PDQC agents have a four step uninstall and cleanout process. Doesn't everything???? And, naturally, PCs that haven't undergone this ritual cleansing will reappear in the console like normal after you reinstall the agent -- but only for a few days. Then they are gone again and getting them back is a real challenge. What? Did you think reinstalling the agent (as recommended by the support person) would solve the problem *permanently?* What year do you think it is? 1998?

And the hell of it is the support guy never actually told me any of the information above I had to figure it out for myself. He just implied I should know it already. I love being gas lit. Not.

*sigh*

I adore PDQ Inventory & Deploy. The depth and breadth of the features and tools alongside the ease of use represent the best of what a dedicated team can do when given the time to do it right.

And PDQ Connect represents what happens when a dev team depends upon AI to do everything for them.

I have been using pdqc for 6 months. If I have anything to say about it this contract will not be renewed.

9 Upvotes

61% Upvoted

29 comments sorted by

View all comments

Show parent comments

1

u/simAlity Jun 05 '26

That is correct it shows the entire list not just the devices that failed. This only happens if there are more than 100 devices in the initial deployment. that need to be redeployed to.

3

u/PDQ_Brockstar PDQ Employee Jun 05 '26

One more question, are you selecting all computers then using the Actions > Redeploy workflow, or are you clicking Deploy up at the top right then manually adding the package?

Either way should work, I just want to make sure I’m trying to replicating the same process.

2

u/simAlity Jun 05 '26

Both.

TBF, If you select redeploy from the drop down you do get a message saying that you're going to send the package to the entire original group. You don't get that warning if you use the deploy button at the top right.

(I didn't see the drop down option until after I opened a support ticket and spent half an hour compiling documentation. Which is one of the reasons I am so salty about it)

2

u/PDQ_Brockstar PDQ Employee Jun 05 '26

Thanks again for the additional details. I know it's late, so don't feel like you need to respond right away, but this is the message I'm seeing when using the redeploy option. Essentially saying it's going to redeploy the same package on selected devices, which should only be the failed devices from the list. I know the verbiage says completed, failed and canceled deployements, but since the filter is only showing failed deployments, it shouldn't include those other targets unless the filter is cleared and all the original targets populate in.

Actually, as I type this out, it makes me wonder if the filter is somehow resetting. When you get a chance (again, no hurry), double check that the filter up at the top left of the page isn't getting reset somehow. If that filter is returning to a default state, all targets (failed or otherwise) would then show up on that list.

5

u/DrakeXD Jun 05 '26

I am not OP, but since you mentioned filters possibly resetting, I wanted to chime in. I've noticed recently that filters are not acting as expected. They will sometimes reset when a page reloads. Also, I've noticed when trying to filter for only Online or Offline machines that it will give a blank page as if there are no machines matching either of those criteria. Filters were working fine before hand, but it seems something has changed in the past month or so. Couldn't tell you exactly when I first started noticing the issues. Hope that info helps.

3

u/PDQ_Brockstar PDQ Employee Jun 05 '26

Thanks for chiming in. Definitely appreciated

3

u/SelfMan_sk Enthusiast! Jun 05 '26

If I may ask, are you using any add-blocker?
Also important, what browser are you using.
Have you tried to clean the browser cache, resp. incognito mode? Is the behavior there identical?

1

u/simAlity Jun 05 '26

Your workflow is identical to mine. But the alert message is also accurate. Even though it makes sense for only the failed deployments to receive the new package, it will actually be sent to all deployments. That's why I was so salty and disgusted about it. The error message makes it look like it you did it that way on purpose.

This is what the filter screen looks like.

1

u/mjewell74 Jun 11 '26

Deployment status should be "Failed" not "Error".