![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I create a package to call other packages in one workflow ,it's very similar as below: Steps----on success--->step2----on success---->step3 - -----on failure--->step4 for step2, if it runs on success, step3 will run continuous, if it runs on failure, step4 will run continous. However, I found that step4 don't run if step2 will run on failure. Is there a way to control right workflow logic. thanks for any help ![]() -- Developer QA Dashboard Microsoft China Development Centre |
#3
| |||
| |||
|
|
Are you looking for something like Introduction to Workflow (http://www.sqldts.com/default.aspx?287) "Microlong" <Microlong (AT) email (DOT) com> wrote in message news:Microlong (AT) email (DOT) com: I create a package to call other packages in one workflow ,it's very similar as below: Steps----on success--->step2----on success---->step3 - -----on failure--->step4 for step2, if it runs on success, step3 will run continuous, if it runs on failure, step4 will run continous. However, I found that step4 don't run if step2 will run on failure. Is there a way to control right workflow logic. thanks for any help ![]() -- Developer QA Dashboard Microsoft China Development Centre |
#4
| |||
| |||
|
|
No, I don't know the reason why the step4won't run when step2 failed ? Do you have experience on this case ? "Allan Mitchell" wrote: Are you looking for something like Introduction to Workflow (http://www.sqldts.com/default.aspx?287) "Microlong" <Microlong (AT) email (DOT) com> wrote in message news:Microlong (AT) email (DOT) com: I create a package to call other packages in one workflow ,it's very similar as below: Steps----on success--->step2----on success---->step3 - -----on failure--->step4 for step2, if it runs on success, step3 will run continuous, if it runs on failure, step4 will run continous. However, I found that step4 don't run if step2 will run on failure. Is there a way to control right workflow logic. thanks for any help ![]() -- Developer QA Dashboard Microsoft China Development Centre |
#5
| |||
| |||
|
|
Yes step 4 will not run because of a failure on Step 2 because it has no idea about step 2 or rather it never gets told to wake up and look around. Step 3 should not execute if 2 fails either because you use an ON SUCCESS constraint and it did not succeed. You will either have to add an ON ERROR constraint + step to every work step you do or get sexy by skipping steps but that could be more trouble than it's worth. Allan "Microlong" <Microlong (AT) email (DOT) com> wrote in message news:Microlong (AT) email (DOT) com: No, I don't know the reason why the step4won't run when step2 failed ? Do you have experience on this case ? "Allan Mitchell" wrote: Are you looking for something like Introduction to Workflow (http://www.sqldts.com/default.aspx?287) "Microlong" <Microlong (AT) email (DOT) com> wrote in message news:Microlong (AT) email (DOT) com: I create a package to call other packages in one workflow ,it's very similar as below: Steps----on success--->step2----on success---->step3 - -----on failure--->step4 for step2, if it runs on success, step3 will run continuous, if it runs on failure, step4 will run continous. However, I found that step4 don't run if step2 will run on failure. Is there a way to control right workflow logic. thanks for any help ![]() -- Developer QA Dashboard Microsoft China Development Centre |
#6
| |||
| |||
|
|
I create a package to call other packages in one workflow ,it's very similar as below: Steps----on success--->step2----on success---->step3 - -----on failure--->step4 for step2, if it runs on success, step3 will run continuous, if it runs on failure, step4 will run continous. However, I found that step4 don't run if step2 will run on failure. Is there a way to control right workflow logic. thanks for any help ![]() -- Developer QA Dashboard Microsoft China Development Centre |
#7
| |||
| |||
|
|
I create a package to call other packages in one workflow ,it's very similar as below: Steps----on success--->step2----on success---->step3 - -----on failure--->step4 for step2, if it runs on success, step3 will run continuous, if it runs on failure, step4 will run continous. However, I found that step4 don't run if step2 will run on failure. Is there a way to control right workflow logic. thanks for any help ![]() -- Developer QA Dashboard Microsoft China Development Centre |
![]() |
| Thread Tools | |
| Display Modes | |
| |