on 2007 Jan 15 9:42 AM
Hi All,
I am facing a very atypical issue which I will try and explain below:
When a workflow is triggered in the system, the first step of the workflow is a background step. Now Ideally, I would have expected this step to change from "READY" state to "INPROCESS" within a fraction of a second. What happens with our workflows is that these steps continue to remain în "READY" state for 2-3 hrs. Please note that there is no deadline monitoring active for these steps.
I have 2 questions based on this:
1. How does the workflow system function with regard to changing a step state?
2. More important question : Why is this above mentioned problem occurring in our system? Is it something to do with system performance?
I gave the first step as an example. This does not necessarily happen at the first step. This may happen at any step in the workflow(being stuck as ready status).
This is happening across the entire workflow system in workflows developed for all modules.
Thanks in advance.
Ashish
Hi,
If you are seeing the LOG of the workflow and if you have find the state as READY means that the workflow has sent mail to the corresponding agent for execution. In case of background processing it means that the program is set for background processing.
Regards,
Ramu N.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
62 | |
12 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.