You need to capture the api sql filter logs also when this escalation runs. (Or you can manually run the escalation just to capture these logs).
This will give you filter which is throwing the error.
Just add extra action which will set the actual start and end date and fire the delete query which might solve your problem.
Thanks for taking interest in this.
I had gathered the logs when the issue manifested itself.
The logs are huge but I am attaching the relevant snippets from the logs. Please search for "SYS:CLN:TA@00:05-StartCleanUp" and you will notice that it's occuring twice in the snippet I have provided. I followed your suggestion but have been unable to figure out the right filter so far.
I have attached two snippets, both are from the same logs basically. The second one has more content.
Would you please guide me further on this?
Thanks for taking interest in my issue.
What you are saying sounds extremely plausible, since that's the error I am seeing immidiately after the concerned escalation viz. "SYS:CLN:TA@00:05-StartCleanUp" tries to execute. I have attached two snippets of logs, both are the same except that I made sure the second one has more info than the first. The latter is concide and short while the former is more exhaustive.
Just search for "SYS:CLN:TA@00:05-StartCleanUp" in the attached log snippets.
The thing is, I can't figure out which filter is responsible for purging orphan tasks.
Also, I am clueless as to where should I add the extra action which will set the actual start and end date and how should I fire the delete query?
Would you please help me ahead?
OK the logs does not filter action.
Check the filter TMS:TAS:ActualDateReq_OnClosed . I think this is throwing the error. May be trying disabling this and run escalation again and see if you get an error. Revert it after testing.
Thanks Will try and revert.
I am doing this in production environment.
Just wanted to ensure I can disable the filter and run the escalation without worrying about any negative impact?
Make sure you perform test in non-working hours.
Filter is generally throwing error for dates field so it would stop giving errors even in valid scenarios. So you are testing in out of business hours then no issue. - Make sure to revert it online once done testing.
Also running escalation after hours is no issue.
I found something interesting.
When I ran a search in the Developer Studio using the filter you provided, I actually got two filters.
I opened both of these filters and found differences only in "Run if Qualifications". Everything else is same.
What do you think?
Thanks for taking interest so far.
ABYS filters on task are generally process designed task. Ignore the one with ABYS.
If ABYS filters are to be ignored, is something wrong with Run if Qualification of TMS:TAS:ActualDateReq_OnClosed ?
I am not able to figure out what zTmpGroupClose does?
I am guessing this is used when task is part of task group. You can check the value in this field from db for normal task and task from group.
Ok, will look into this.