Skip to Content

Delay to start work item

Hi Gurus,

Could someone tell me the reason for a workitem start late, a time interval between the creation date and the start date? I already say that it is nothing in the definition of the workitem, since sometimes the delay happens and sometimes it does not happen, starting immediately.

Example with delay

Example without delay, workitem with the same definition and configuration

Em português:

Alguém saberia dizer o motivo de um workitem iniciar com atraso, um intervalo de tempo entre a data de criação a data de início? Já digo que não é nada na definição do workitem, visto que às vezes acontece o atraso e às vezes não acontece, iniciando imediatamente.



workitem1.png (17.7 kB)
workitem2.png (17.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Jul 06, 2017 at 06:40 AM

    This is perfectly normal. Work items are started via RFC in a new session. If the system is busy it will wait. You can see pending RFC calls in SM58.

    If the system is under heavy load it can even take hours. Therefore you should never rely on a specific turnaround time for RFC processes.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Mike,

      I thought it was about server load, but I was not sure.

      Was there an explanation for this delay being exactly 1 minute?

      In the vast majority of cases the delay is exactly 1 minute. Is coincidence?

      Or is it some rfc configuration?

      thank you for now

  • Jul 06, 2017 at 12:45 PM

    Basis might be able to answer some of that. It's not a straightforward "load=slower" effect. The type of load is relevant, and actual execution strategy may vary. If you delve into the technical log, you will probably see reference to a TRFC on the delayed items but not on others. The system will usually execute using synchronous RFC if it has time, and switch to TRFC if it's busy. RFCs, including workflow, may be queued and batched at regular intervals using QRFC. If you see stuff in SMQ1 (I think, no system in front of me right now), then that's probably the case.

    But this is far more detail than needed, the basic idea is that any WF should be expected to be delayed.

    Add comment
    10|10000 characters needed characters exceeded