Hi Markus Just to clarify:
"When switching to user '71187' and executing a 'scancel' to a job from from user '70032' (similar to the last entry of the output above), it is impossible to get a job cancelled." So is user 71187 able to cancel the job submitted by user 70032 with scancel or not? What I've observed is that jobs submitted by pipeline/workflow will be marked as cancelled if the encapsulating pipeline/workflow is cancelled, but the job's state is indistinguishable (CANCELLED) from the result of scancel. However, if non-privileged users as per sacctmgr AdminLevel are able to cancel other people's jobs with scancel, then that's a very different story. No indication that we've ever encountered it here. Regards Jeff
