You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Skip to content
  • Register
    • Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

    Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here
    To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

    For more information, please refer to this announcement explaining best practices for getting answers to questions.

    Synchronize Notifications in Global Header best practices

    in Career and Succession 5 comments

    Summary:

    Synchronize Notifications in Global Header best practices, running more than recommended amount

    Content (required):

    Hi All,

    The Synchronize Notifications in Global Header process aims to synchronize all bell notifications in the system with current statuses of those tasks. Oracle recommends running once every 2 hours (12 runs daily).

    Are there any current negative impacts on system if the process is run once per hour (24 runs daily)?

    What are the pros/cons of running the process at a rate above the Oracle-recommended?

    Best Wishes,

    William

    Version (include the version you are using, if applicable):

    23A

    Code Snippet (add any code snippets that support your topic, if applicable):

    Tagged:

    Howdy, Stranger!

    Log In

    To view full details, sign in.

    Register

    Don't have an account? Click here to get started!