My automated "click" Applescript has just stopped working

Right up until a week ago, my simple Applescript that had to simply click on a specific coordinate on screen just stopped working. Here is the Applescript: tell application "System Events" click at {693, 619} end tell And I automate it's trigger at a specific time of day with the help of osascript (recommended for Applescripts) using the following plist file. Label com.mouseclick.plist ProgramArguments /usr/bin/osascript /Users/mugenvoid/Downloads/mouseclick.scpt StartCalendarInterval Hour 6 Minute 10 I've added this plist file to the LaunchDaemons folder of my core Library folder. This will ensure it's a global daemon, so it should have the highest chance of always triggering correctly. Beyond that, I've given all the relevant access and permissions (Accessibility, Automation, disk access etc) for this setup to work correctly. To ensure the job is loaded correctly and functional, I use an application called Launchcontrol 2. Over there, it is always loaded in correctly and the status shows as OK. Despite all these checks and balances, the script just doesn't click on the specific coordinate no more. It was always working perfectly fine up until a week ago and I haven't made any changes whatsoever to this whole setup. The Launchcontrol 2 application has some launchd(8) logs of the job trigger event at the designated time that I would like to share. Perhaps it will help with the debugging. Here it is: 2024-10-22 06:10:03.808584 internal event: WILL_SPAWN, code = 0 2024-10-22 06:10:03.808688 service state: spawn scheduled 2024-10-22 06:10:03.808692 service state: spawning 2024-10-22 06:10:03.808727 launching: xpc event 2024-10-22 06:10:03.810543 xpcproxy spawned with pid 28683 2024-10-22 06:10:03.810593 internal event: SPAWNED, code = 0 2024-10-22 06:10:03.810599 service state: xpcproxy 2024-10-22 06:10:03.810718 internal event: SOURCE_ATTACH, code = 0 2024-10-22 06:10:03.827675 service state: running 2024-10-22 06:10:03.827703 internal event: INIT, code = 0 2024-10-22 06:10:03.827709 job state = running 2024-10-22 06:10:03.827726 Successfully spawned osascript because xpc event 2024-10-22 06:10:10.104597 exited due to exit(0), ran for 6293ms 2024-10-22 06:10:10.104617 service state: exited 2024-10-22 06:10:10.104630 internal event: EXITED, code = 0 2024-10-22 06:10:10.104633 job state = exited 2024-10-22 06:10:10.104665 service inactive: com.mouseclick.plist 2024-10-22 06:10:10.104681 service state: not running To the best of my knowledge, I've checked everything possible from my end and am still faced with this roadblock. I'd really appreciate your support here! Condensed view of what I've tried so far: - Under the Privacy & Security settings section, I enabled Accessibility for osascript, launchcontrol and the script editors I've used for the Applescript and the plist file. See image attached below. - Under the Privacy & Security settings section, under Automation, the requisite access has been given to Osascript and relevant applications. See image attached below. - Ensured the job is loaded correctly with no errors and that it is loaded in as a global daemon (by adding the plist file to the LaunchDaemons foler in my core Library folder). See image attached below. - Verified the script file and plist file and found no syntax errors (code used for both has been shared above). - Ran the script file from the Script Editor itself to confirm if it's working fine and got the following results. See image attached below.