Open pintomi1989 opened 6 months ago
Hey @pintomi1989, when you get the chance, can you please ask the customer to provide a screenshot / Loom recording of this issue?
We thought there wasn't a real use case around removing all scripts from the queue but it sounds like there might be. As an IT admin, if I queue up a script on a large number of hosts and it starts to error on a few, I want to remove this script from the queue for all hosts.
We didn't have room to bring this into the current design sprint (4.48).
Please feel free to bring this back to feature fest.
From customer-preston:
(per request by for a use case for script purging) Since: we are doing script-based app management on our own we have to sometimes download multi-Gb apps we use one script to install all customer apps And, on the Fleet side of script rules: there is currently no way to manually clear or adjust the script queue scripts will attempt execution 2x if a script needs to run a second time after this it must be queued again re-queue does not clear any previous failures or attempts script history can be obtained with api (or activity feed) but the Fleet UI modal shows the latest (or pending) This is what happens: Our app-install scripts timeout We consider it still running, since it's in the queue, so we do not attempt to run it again Any other script (for recovery key, MB agent, ...) is queued and NOT RUN since the queue can't be purged This is obviously a HUGE problem, since App Management is a key part of any MDM value prop, but especially on SMBs + this blocks any other form of script exec We really need solutions from you on this, starting with but not limited to: More permissive rules around script run time Script purging
Want to reiterate emphasis on this issue per meeting with customer-preston 20240522.
As a Fleet user, sometimes large amounts of scripts get ran in error. It would be useful to have the ability to easily purge the script queue.
Also, if have an endpoint with a "stuck" script, if we end up manually wiping the device, and then re-enroll, the script executes.