How To Fix SWF_RUN_SERVICES035 - System failure during restart execution (Retry scheduled in 24 hours)

SAP Error Message - Details

• Message type: E = Error

• Message class: SWF_RUN_SERVICES - Workflow: Services

• Message number: 035

• Message text: System failure during restart execution (Retry scheduled in 24 hours)

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 SWF_RUN_SERVICES035 - System failure during restart execution (Retry scheduled in 24 hours) ?

  The SAP error message SWF_RUN_SERVICES035 indicates that there was a system failure during the restart execution of a workflow. This error typically occurs when a workflow instance fails to complete successfully and the system attempts to restart it. The message also indicates that a retry is scheduled in 24 hours.
  Causes:
  
  System Resource Issues: Insufficient memory, CPU, or other system resources can lead to failures in executing workflows.
  Database Issues: Problems with the database, such as locks, deadlocks, or connectivity issues, can cause workflow execution to fail.
  Configuration Errors: Incorrect configuration settings in the workflow or related components can lead to execution failures.
  Code Errors: Custom code or enhancements in the workflow can introduce errors that cause the workflow to fail.
  Transport Issues: If the workflow was recently transported from one system to another, there may be inconsistencies or missing objects.
  
  Solutions:
  
  Check System Logs: Review the system logs (transaction SLG1) and workflow logs (transaction SWI1) for detailed error messages that can provide insights into the cause of the failure.
  Monitor System Resources: Use transaction ST02 (buffer management), ST06 (OS monitoring), and ST22 (dump analysis) to check for resource issues or short dumps that may indicate underlying problems.
  Database Health Check: Ensure that the database is functioning correctly. Check for locks or performance issues that may be affecting workflow execution.
  Review Workflow Configuration: Verify that the workflow is correctly configured and that all necessary objects (like tasks, events, etc.) are available and correctly set up.
  Debugging: If you suspect custom code is causing the issue, consider debugging the workflow to identify the point of failure.
  Retry Mechanism: Since the system has scheduled a retry in 24 hours, monitor the workflow instance to see if it succeeds on the next attempt. If it fails again, further investigation will be necessary.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches or updates.
  
  Related Information:
  
  Transaction Codes:
  
  SWI1: Workflow log display
  SWI2_FREQ: Display workflow instances
  SLG1: Application log
  ST22: Dump analysis
  ST06: Operating system monitoring
  ST02: Buffer management
  
  
  SAP Support: If the issue persists after troubleshooting, consider reaching out to SAP Support with detailed logs and error messages for further assistance.
  
  By following these steps, you should be able to identify the root cause of the SWF_RUN_SERVICES035 error and implement a solution to resolve it.