We have noticed one unusual situation when working with Social Miner tasks.
We use Social Miner (CISCO UCCE 11.5) for e-mail tasks and all tasks that we create (through CISCO Social Miner API) are tagged as requeue_on_recovery. When we want to cancel some tasks, we use CISCO Social Miner API DELETE request. After successful DELETE (Cancel) request we noticed that we could see these tasks as DISCARDED on Social Miner and these tasks still have tag requeue_on_recovery. Situation that we noticed is when SocialMiner recovers after a failure event, Social Miner “removes” all tasks, in QUEUED state, and recreates (requeue) them back.
Is it possible that Social Miner in this recreation process also recreates tasks that where DELETED / Canceled through API (tasks that should not be recovered because they were deleted)?
