Im getting loads of these service user login issues(1311) in my scheduled jobs

I periodically am getting schedules failing because of this error, so for a job that runs 6 times a hour, 2 out of 6 will fail with this error:

Error executing job: Failed to login user (1311). System.ComponentModel.Win32Exception (1311): We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

Some info around the setup:
2 Node Setup, SQL database backend(is in a 2 node AG as well)
Repo is hosted on a UNC path but added via c:\PSU** as a sys link
PSU runs via a gmsa account
Have multiple other service accounts as variables which then the schedules use for their jobs

ive traced and logged the connection to the DC's all night on multiple nights, but the connection is always there no fluctuation in stability, cant be the credentials since its a GMSA account

Its pretty annoying having to hope for a schedule to run since its important they run reliably, when they need to run.

Can anyone please give me some pointers or support on this? Let me know if i can provide more information!