That sounds like you have a delay on the time job. Did you
at any time maybe do some SharePoint clean up? Ie, deleted list
items/Lists/Library or sites on which there was K2 SP integration? Also do you
perhaps have Escalations on the SharePoint Workflow Integration Client events
that Expires the activity or doe a GOTO?

Please run the following SQL query and attach the results to
the thread.

Select * from ScheduledWorkItems where [type]=
'DE890E35-7940-44A4-9130-1DED680765B6'

Run this against the SharePoint Content db. Ie [WSS_Portal]

Vernon

Looks like I have 256 items sitting in this table. I checked out the XML in TextPayload field and it has a reference to the site form the deleted site collection. How to force SharePoint timer job to delete those items?

I tried to update InternalState and DeliveryDate fields but this trick was not working. Timer Job just rescheduled all items to 21pm.

 update ScheduledWorkItems set InternalState=8, DeliveryDate= DATEADD(MINUTE, 10, GETDATE()) where 0TYPE]= 'DE890E35-7940-44A4-9130-1DED680765B6'

That sounds like the timer
is clogged with jobs that are possibly orphaned. What version of K2 are
you running? Also in my previous post, is it a possibility that you have GOTO
or Expire Activity escalations on the SharePoint Workflow Integration Client
event? And/or did you do any SharePoint clean up recently? Ie, deleted list
items/ lists/libraries or even sites?

I would also suggest you log
a K2 Support ticket for this issue to get it resolve asap. Please post back the
ticket number and include the info as requested above as well as an export of
the Select statement in my previous post.

Vernon

Sorry
for that I only now noticed that you said you deleted a site collection. I play
with this scenario, in the meantime please get a Support ticket logged and
reference this thread.

Vernon

We managed to reproduce and
create orphan jobs using this scenario. Please ensure a K2 support ticket is logged
and post the ticket number. This way I can follow up using the ticket as a reference
and help you in a timely manner.

Vernon

I deleted all orphan jobs and everything is working again.

Great glad
you got is solved. Just to close off the thread. The K2 failover timer picks up
100 jobs on the minute every minute. If you have orphaned jobs these might clogged
the timer job and cause delays in the creation of Tasks in SharePoint.

To solve
this you will have to clean up all orphaned jobs, there are different scenarios
to put a job in an orphan state. Any Sharepoint clean up, deletion of List
items, deletion of lists or libraries, deletion of site collections, GOTO or
expire Activity escalations, etc.

Most of
these are not an issue OOTB running the latest K2 version (4.6.4), this specific
scenario however will be addressed in the after next release (4.6.6).

If any
questions, please don’t hesitate to contact K2 support.

Vernon