Can you share more details, whether the form has a direct connection with the DB, or does the form submission trigger a LiveCycle workflow/ process which puts entries in the DB?
lastly , are we placing these entries in a custom table within LC's schema ?
Hi Sid, Thanks for ur reply.
BTW the form which we submit will be mapped via workflow and then the data will be updated in database. Also these entries will be placed in a table created by the server. kindly let me know if you need any other details regarding form submission
1 person found this helpful
Is this happening with any other workflows in the environment as well , or is this the only one.
And if so, has this workflow been used extensively in the recent past ?
We will first need to find, whether your workflow gets triggered , during the problem phase or not.
You will need to find a time span, when there's least activity on the server.
then try to submit a form, and see if that triggers the workflow ?
2 ways to find whether process/worflow got triggered or not - either check the tb_process_instance table in the LC database, and see if there's a new entry there ?
Or turn on recording for your process (using workbench) and see if anything gets recorded. (dont do this during business hrs, else you'll be flooded with recordings)
If the process does get triggered, then the recording will show whether the workflow gets stuck at any point.
Anything in the logs , especially when you face the problem?
Sid - This issue is happening in almost all the workflows now. Also added point is, it always happens in Production server and we never faced this in development server. Is there something we need to find at this point?
This is almost happening in 1st or 2nd step of workflow. In this case you are right. we checked for new entry in table. It will be created, process id will be there and values will not be updated in database (in workflow variable or xml)
There are no recordings in server log when this problem arises. everything seems to be normal but values will not be updated in database.
Also for temporary fix we replaced particular user QPAC with new one. After that this problem didnt happen for few months then again it is happening. As these forms are highly used in Production, so we are in need to find the permanent fix.
you will have to turn on process recording from workbench to inspect that particular workflow.
then invoke the process and review recordings from workbench. That should show us step by step, how far the proces has moved.
Also what's the LC version in use ? 7.x/8/x 9.x/10.x/11/x ?
if it;s happening with all processes how come, replacing QPAc helps all of them.
Is this a custom component ?
what;s the step in your workflow, beyond which things dont seem to move. is that an assignTask operation ?
we cant troubleshoot this much over forums. Maybe you should open a ticket with LC enterprise Support team to investigate as well.