Scheduled Orchestrations are not triggering due to "username ... is not a valid user" errors
(Doc ID 2452130.1)
Last updated on SEPTEMBER 28, 2018
Applies to:Autonomous Integration Cloud - Version 18.2.5 and later
Information in this document applies to any platform.
Scheduled Orchestrations are not triggering.
The diagnostic logfiles show the underlying cause is due to "username ... is not a valid user" errors.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document