Wake Up Sequential Workflow Service -


i need able "wake up" sequential workflow service - , concept worked in state machine i'm not understanding why doesn't work in sequence. below picture of workflow.

orchestrator sequence

this workflow used orchestration of other workflow services. literally needs run forever - need ability shut down softly. had same type of thing implemented in state machine, delay trigger 1 transition , receive trigger another. long first mentioned transition wasn't running able receive take message , transition final state. here want do, can see, set boolean value false indicating while loop should exit , workflow terminate.

please me understand why isn't working.

thanks all!

edited diagnostic output

32: activity [1] "main sequence" scheduled child activity [4] "while" 33: activity [4] "while" executing {     variables         continuerunning: true } 34: activity [4] "while" scheduled child activity [6] "visualbasicvalue<boolean>" 35: activity [6] "visualbasicvalue<boolean>" executing 36: activity [6] "visualbasicvalue<boolean>" closed {     arguments         result: true } 37: activity [4] "while" scheduled child activity [8] "pick" 38: activity [8] "pick" executing 39: activity [8] "pick" scheduled child activity [9] "soft exit branch" 40: activity [8] "pick" scheduled child activity [26] "process branch" 41: activity [26] "process branch" executing 42: activity [26] "process branch" scheduled child activity [42] "delay" 43: activity [42] "delay" executing {     arguments         duration: 00:01:00 } 44: activity [9] "soft exit branch" executing 45: activity [9] "soft exit branch" scheduled child activity [14] "soft exit sequence" 46: activity [14] "soft exit sequence" executing {     variables         __handle1: system.servicemodel.activities.correlationhandle } 47: activity [14] "soft exit sequence" scheduled child activity [21] "soft exit" 48: activity [21] "soft exit" executing {     arguments         correlateswith: system.servicemodel.activities.correlationhandle         parameter0: system.servicemodel.activities.correlationhandle } 49: activity [21] "soft exit" scheduled child activity [21.1] "sequence" 50: activity [21.1] "sequence" executing {     variables         requestmessage:          receivenopersisthandle: system.activities.nopersisthandle } 51: activity [21.1] "sequence" scheduled child activity [21.6] "internalreceivemessage" 52: activity [21.6] "internalreceivemessage" executing {     arguments         correlateswith: system.servicemodel.activities.correlationhandle         nopersisthandle: system.activities.nopersisthandle         parameter0: system.servicemodel.activities.correlationhandle } 53: workflowinstance "main sequence" idle 54: workflowinstance "main sequence" persisted thread '.0' (0x1fa4) has exited code 0 (0x0). thread 'debuggerthread:soft exit branch.1' (0x13b4) has exited code 0 (0x0). 55: workflowinstance "main sequence" unloaded 

you should tracking data - understand going on. see troubleshooting workflow services diagnostic logging


Comments

Popular posts from this blog

jasper reports - Fixed header in Excel using JasperReports -

media player - Android: mediaplayer went away with unhandled events -

python - ('The SQL contains 0 parameter markers, but 50 parameters were supplied', 'HY000') or TypeError: 'tuple' object is not callable -