Continuation IsComplete

Aug 19, 2009 at 8:06 PM
Edited Aug 19, 2009 at 8:07 PM

This is a great tool. It helped me in generating a generic BAM service (kinda!) that would handle multiple activities without explicitly exposing all the activity details for each activity.

I am seeing an issue with Continuations. When continuation is enabled, "isComplete" flag in "XXXX_Active" tables is not set to true. What this is doing is making the records that are complete (endAcitivy called on them) still be in XXXX_Active tables which slows the process.

The code structure is as below. One section of the process would do the folowing

  • BeginActivity
  • EnableContinuation
  • CommitActivity

and another section of the process would do the following

  • CommitActivity
  • EndActivity

All activity items are getting populated but the flag does not get set. I am using Direct Event Stream.


Feb 16, 2010 at 9:54 PM

The part of the process that begins the activity and enables continution must also call EndActivity.  It seems counter-intuitive, but it's true.  If you add EndActivity to the end of your first process, you will probably see the correct results.