Process remains in WAITING mode in the Active Processes window

kklosson

I have a process that never completes and remains in the Active Processes Window in Waiting status for a good number of hours or until canceled. The process clearly completes all actions. This is true in test and production environments. Due to the nature of my application, I get quite a number of these each day, often with many stacked up in the Active Processes window. I have even issued an END PROCESS statement at the end of the process with no change. Any suggestions are welcome. Also, I can’t tell if these processes are consuming resources. Does anyone know?

customaware

Have your cleared out you Execution Contexts lately? Might be some old one hanging around

kklosson

Yes. I check it all the time. Also, same result on my dev environment.

customaware

Have you tried turning on the PROFILER to see if that can spot the issue?

aware_support3

Is the problem reproducible in a small BSV? If so can you provide this with instructions on how to replicate the error.

kklosson

aware_support3

Here is an interesting finding. The process is a form submission with a number of actions and the final rule is to log out the user:

DISPLAY PERSPECTIVE VPLogout

When I rem out this rule, the process quits normally. And as stated, I tried including a final rule: END PROCESS, which did not clear the process. I can only speculate that something in displaying a new VP abandons the process in some way that it does not finish. I believe this can be duplicated by creating a simple process that does something like opening a form and attach a process to the save action that ends with:

DISPLAY PERSPECTIVE VPLogout

In a private browser session, login as administrator and monitor the process in the Active Processes window. When the process completes, refresh the window to observe whether the process completes or remains present.

I tried changing the DISPLAY VP action to call a secondary process which does the same. In that case, both processes remain in waiting, so that’s no good.

I have also tried using the LOGOUT action, but it always presents a waiting screen that never resolves, for example:
FIND SystemUser Where SystemUser.ID = LoggedInSystemUser.ID
LOGOUT SystemUser

This and a few other variants result in a waiting screen.

nhofkes

It may be different from your specific case, but I recently discovered that when I use EXEC_STRING to dynamically start a process that has user interaction, like DISPLAY LAYOUT or VIEW/EDIT BO, that process would never terminate except after a time out. Theoretically this could be avoided if you could add END PROCESS to the string that is passed to EXEC_STRING, but that results in a syntax error - apparantly you can you use only one action for the string.