3/25/2017 11:20:36 AM

This blog will tells Delay in executing a Workflow-There is a delay in starting a workflow. There is a delay in executing workflow step.

Cause

If there is a large load in the system (many workflow at one time) this can cause a backlog in SM58.

There may be a lack of resources to execute the tRFC's.

Resolution

There may be 2 possible reasons why there is a delay:

[1] Event Queue 

If you are using the event queue to deliver the event, maybe it is being queued and this is causing the delay. Check in transaction SWE2 and


see if the event queue is active for the object event and workflow template. Also check transaction SWEQADM and SWEQBROWSER.



[2] SMQS

Another possibility would be if you are using SMQS with the workflow RFC destination assigned. Please check in transaction

SMQS and see if WORKFLOW_LOCAL_XXX (XXX = client) is registered. Now check in SM58 to see if there are entries here with "Transaction Recorded".  

(2.1) Speed up processing:
The only way to speed up the processing of the current entries in SM58 is to increase the max conn. value for the particular destination in SMQS. 
Please increase this and it will gradually reduce the backlog in SM58. 
(By default Max Runtime is 60 sec, if one of the connection's runtime exceed 60 sec then all other RFC LUWs have to wait until the remaining one is finished, this is the System design)

(2.2) rdisp/rfc_check:
Check what value parameter rdisp/rfc_check currently has via transaction RZ11. It should be set to 2 

(2.3) rdisp/rfc_use_quotas:
Check what value parameter rdisp/rfc_use_quotas has via transaction RZ11. You should not change the default value of 1.

(2.4) rdisp/rfc_min_wait_dia_wp
Check what value parameter rdisp/rfc_min_wait_dia_wp currently has via transaction RZ11. The default value is 1.  
If this is set to high, it may cause issues.  For example if it’s set to 5 and you only have 7 dialog work processes in total. This means that you should keep 5 dialog resources free for non-rfc tasks. So only 2 are available for RFC requests.
You will also probably see a message in transaction SARFC that “Resources are NOT ok” if that is the case.

(2.5) Name of AS Group (In SMQS):
You can specify your own AS Group and assign specific servers if you wish. You can setup a group via RZ12 and assign it in SMQS. All destinations registered in SMQS will then use the logon group specified in SMQS (not just workflow).
Check the resources for your AS Group via SMQS menu Goto => QRFC Resources and see if there is an issue.

If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.


COMMENTS