I am facing an issue with transaction scope activity commit.
I have a simple workflow with two sequential activities A1 and A2 within a transaction scope (default isolation level and timeout).
I have made sure that i have added the sql presistance service added to the workflow.
Now A1 and A2 are very simple activites that insert into table T1 and T2 respectively (sql 2005).
When i run my workflow i see that A1 and A2 are executed without any errors ( i checked the tables ÃÂ and found the records inserted with read uncommited)
but the debug point does not get out of the trasaction scope activity .... it looks as if the workflow is suspended (though not really) and later gets out of the scope and rolls back the inserted data.ÃÂ
I am sure that there was no error in executing the two activities.
Why does this happen? Can somebody ÃÂ help me with the missing piece.
View Complete Post