Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix SR086 - Restart condition set. Wait for queues with higher priority


SAP Error Message - Details

  • Message type: E = Error

  • Message class: SR - RFC utilities

  • Message number: 086

  • Message text: Restart condition set. Wait for queues with higher priority

  • Show details Hide details


  • Self-Explanatory Message

    Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

    To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

    Unfortunately, there isn't any extra information in this error notice.



    What else can you do?

    First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

    Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

    You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.


Smart SAP Assistant

  • What is the cause and solution for SAP error message SR086 - Restart condition set. Wait for queues with higher priority ?

    The SAP error message SR086: Restart condition set. Wait for queues with higher priority typically occurs in the context of SAP's background processing or when dealing with the SAP Service Runtime (SR) framework. This message indicates that a certain process or job cannot proceed because it is waiting for other jobs or queues that have a higher priority to complete first.

    Cause:

    1. Job Priority: The job you are trying to execute has a lower priority compared to other jobs that are currently running or queued. SAP manages job execution based on priority levels, and lower-priority jobs will wait until higher-priority jobs are completed.
    2. Resource Contention: There may be limited resources (like memory, CPU, or database locks) available, causing the system to prioritize certain jobs over others.
    3. Configuration Settings: The system may be configured in such a way that certain queues or jobs are always given precedence over others.

    Solution:

    1. Check Job Priorities: Review the priority settings of the jobs in the system. You can do this using transaction codes like SM37 (Job Monitoring) to see the status of jobs and their priorities.
    2. Adjust Job Priorities: If necessary, adjust the priorities of the jobs to ensure that the one you want to run can proceed. This can be done in the job definition settings.
    3. Monitor System Resources: Use transaction codes like ST02 (Tune Summary) or ST04 (Database Performance Analysis) to monitor system performance and resource usage. If resources are constrained, consider optimizing the workload or increasing system resources.
    4. Check for Long-Running Jobs: Identify any long-running jobs that may be blocking the execution of your job. You may need to terminate or reschedule these jobs if they are not critical.
    5. Review Queue Management: If you are using queues (like in a distributed system), ensure that the queue management is set up correctly and that there are no issues with the queue processing.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as:
      • SM37: Job Monitoring
      • SM66: Global Work Process Overview
      • SM50: Work Process Overview
      • ST22: Dump Analysis
    • SAP Notes: Check SAP Notes for any known issues or patches related to job scheduling and processing.
    • Documentation: Review SAP documentation on background processing and job scheduling for best practices and configuration guidelines.

    If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:
  • SR085 A lock has been set for the queue
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • SR084 LUW data is temporarily locked
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • SR087 This LUW has further predecessors
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • SR088 Generic stop set
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author