Integration scheduler failing with "this user account(s) has been deleted,disabled,locked out or exp
SummaryUser account locked
This is a seemingly random failure and happens on different developers' ids. The last incidents where not preceded by a warning email from Oracle that the user account was locked. And in fact, since our systems use SSO, there should be no issues with account locking. Does anyone have a similar experience?
Can anyone point me to a way to change the schedule user it to something generic so that the random user lockouts will not stop our scheduled integrations from running?