API for getting the start_time of any workflow instance.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2011 05:26 PM
Hi All,
I have a use-case where we need to monitor the workflow instance execution time. If any instance is taking more than a specified time we have to red-flag that instance.
In order to do this we need to get the running instance start time. we tried to look into ACT_HI_PROCINST. This table has process start and end time. But there is a catch, if the work-flow instance is still running this table doesn't contain the information, but it contains the information if workflow involve any usertask or crashes in between.
Most of our workflow doesn't have usertask. So ACT_HI_PROCINST table will not serve the purpose.
Now we want any API which should give the start time of any workflow-instance if we provide the work-flow instance Id.
any help will be greatly appreciated.
I have a use-case where we need to monitor the workflow instance execution time. If any instance is taking more than a specified time we have to red-flag that instance.
In order to do this we need to get the running instance start time. we tried to look into ACT_HI_PROCINST. This table has process start and end time. But there is a catch, if the work-flow instance is still running this table doesn't contain the information, but it contains the information if workflow involve any usertask or crashes in between.
Most of our workflow doesn't have usertask. So ACT_HI_PROCINST table will not serve the purpose.
Now we want any API which should give the start time of any workflow-instance if we provide the work-flow instance Id.
any help will be greatly appreciated.

Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2011 05:49 AM
As you mention yourself, the time info is only saved at wait states. Writing your own operation around the start, saving the timestamps is the only workaround I can think of if you dont want wait states.
But then again, doesnt your process contain any wait states? It seems very unhealthy to me to keep your database transactions open for so long.
But then again, doesnt your process contain any wait states? It seems very unhealthy to me to keep your database transactions open for so long.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2011 11:45 AM
We are not keeping the session for a long time. we are writing a demon which gets up and check the process execution time and my workflow wouldn't have any wait task.
well currently we are storing the process start time in different table.
@jbarrez Thanks for your response
well currently we are storing the process start time in different table.
@jbarrez Thanks for your response

