Delete Timeout

0

Hi,

could you copy the configuration of the timeout?

If the timeout executes a path, the insert condition is evaluated again. If this is false then the timeout should no longer be created and once all timeouts are removed from the database, you should be able to remove it from Designer Studio.

Best regards,
Daniel

Right now it's totaly empty.
Type: Do action
SQL - empty
Daily, 90 days inteval, execute once.

I've tried give SQL wich is always wrong 1=0, but it's still going to the list of timeouts

Hi,
have you tried just adding the condition "SELECT 0"

It killed whole workfolw. So bad idea.

sorry but I don't understand.
If you add such a condition then simply the timeout will not be added to new documents - that's all.

Why would it kill the whole process?

It's not like that.
This condition is wrong, so every time element will enter this step it gives SQL error.
If i add condition like
SELECT WFD_ID FROM WFElements WHERE 1=0 (so it's also always wrong) TIMEOUT still goes to the list of tieouts.
And System tries in specified time run it.
But timeotu still exist in list so can't be deleted.
I need a solution to remove specific TIMEOUT from Timeout list so i can DELETE TIMEOUT complety.
Now i recive error from Studio.

I use this SQL to list all timeouts:

SELECT
ELM.WFD_Signature,
TIM.TIM_Name,
TIM.TIM_Interval,
TIM.TIM_RepeatCount,
TIM.TIM_WFCONID,
TIM.TIM_InsertingSQL,
TIM.TIM_Description,
DATEDIFF(SECOND, TMO.ETM_StartTimeoutTime, TMO.ETM_TSUpdate) AS Delay,
FROM
WFElementTimeouts TMO
INNER JOIN
WFElements ELM ON TMO.ETM_WFDID = ELM.WFD_ID
INNER JOIN
WFTimeouts TIM ON TMO.ETM_TIMID = TIM.TIM_ID

Hi,
I checked both conditions: "SELECT 0" and "SELECT WFD_ID FROM WFElements WHERE 1=0"
for both new timeouts are no longer created when entering a step.

Of course adding a condition does not affect previously created timeouts.

However, going through the path (exiting and entering the same step) causes previous timeouts to be removed and then you can remove such a timeout in Designer Studio (I checked)
But if you have a lot of elements with such timeouts, I don't know if this is a good solution for you (I would have to do a action to move of many documents - technical save path)

I Have about 3,5k Total documents, so it's a lot.
Select 0 as 'X' works