Hello,

Did you found a solution? I have the same problem.

Thanks in advance.

If the flow is returning -1 for records being deleted, it's probably because a previous run was canceled before it was finished, or because two instances of the flow were executed at the same time..

The fix for me was to log into the database and clear the row that represented the lock, per:

DELETE FROM OO_TABLE_LOCKS WHERE NAME = 'PURGE_ALL';
-- then commit, depending on the DB platform...
COMMIT;  

If the flow is returning -1 for records being deleted, it's probably because a previous run was canceled before it was finished, or because two instances of the flow were executed at the same time..

The fix for me was to log into the database and clear the row that represented the lock, per:

DELETE FROM OO_TABLE_LOCKS WHERE NAME = 'PURGE_ALL';
-- then commit, depending on the DB platform...
COMMIT;  

The flow  is returning the number of deleted records, but nothing is being deleted since when I check the “database health” , the amount of  “debugger usage” remains the same.

1. Stop Central and Backup your DB.

2. Execute these query to make sure no flows are in running/pending state:

UPDATE OO_EXECUTION_SUMMARY SET STATUS = 'CANCELED', END_TIME=START_TIME WHERE STATUS IN ('RUNNING','PAUSED','PENDING_PAUSE','PENDING_CANCEL');

3. Purge Debugger Events

TRUNCATE TABLE OO_DEBUGGER_EVENTS;

Hi Don
thanks for sharing this info.
just run the 'purge execution summary' and within less a minute it finishes on error,
by this reason 'The request could not be completed', which I could not find
much.
but right after the execution of your queries take place, should I run the flow?
best wishes
Raphael