Problem with our central at the expiration time of the flows.
We have a problem with our central at the expiration time of the flows. Currently, configurate on 120 minutes, normally this time allow to cancel flows when the value expires. But that is not the case. In fact, at the end of this periode the flows seem to have been canceled because they are no longer visually present on the flows execution page on the central.On the other hand, these flows continue to exist in the database. When this happens, we restart the hpoo services on the RAS where the flows are still available. If after this step the flows are still running in the database we do a "truncate table".
TRUNCATE TABLE OO_FINISHED_BRANCHES;
DELETE FROM OO_SUSPENDED_EXECUTIONS;
TRUNCATE TABLE OO_EXECUTION_QUEUES;
TRUNCATE TABLE OO_EXECUTION_QUEUES_1;
TRUNCATE TABLE OO_EXECUTION_STATES;
TRUNCATE TABLE OO_EXECUTION_STATES_1;
TRUNCATE TABLE OO_EXECUTION_STATES_2;
DELETE FROM OO_EXECUTION_SUMMARY WHERE STATUS NOT IN ('COMPLETED','CANCELED','SYSTEM_FAILURE');
UPDATE OO_TRIGGERS SET TRIGGER_STATE='WAITING' WHERE TRIGGER_NAME='splitJoinTrigger';
This problem becomes recurrent, do you have a solution, please ?
(HPOO version 10.70)
Re: Problem with our central at the expiration time of the flows.
What do you mean they dissapear from the Run Explorer?! The user checking those runs has the right permissions to view those flows? For sure there is no filtering applied on the Run Explorer?
Is this generic behavior when it comes to the timeout feature or this is something that happens to you only for some specific flows?