|
Home > Archive > BizTalk Server General > September 2005 > bypass suspended messages from operations in HAT
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
bypass suspended messages from operations in HAT
|
|
|
| Hi everyone
I have an orchestration and scope defined, and an exception block for any
error that will occur. I know what the error will be and thus handle it
appropriately. But i still get a suspended entry within the HAT
Operations->Messages. I am wondering whether it is possible for errors that
have been handled with exception code blocks to bypass the
Operations->Messages area. Still be in the summary area of the HAT but just
not require the user to highlight the suspended message and terminate it.
| |
|
| On Thu, 22 Sep 2005 23:09:01 -0700, Ben wrote:
> Hi everyone
> I have an orchestration and scope defined, and an exception block for any
> error that will occur. I know what the error will be and thus handle it
> appropriately. But i still get a suspended entry within the HAT
> Operations->Messages. I am wondering whether it is possible for errors that
> have been handled with exception code blocks to bypass the
> Operations->Messages area. Still be in the summary area of the HAT but just
> not require the user to highlight the suspended message and terminate it.
What is state of the orchestration instance and what is the message state?
| |
|
| The Orchestration instance finishes executing as normal and leaves the
operations->service instances, whereas there is a single message left in the
suspended state which indicates the error. I know why the error has occured
and just dont want the "LIVE" part of HAT filling up with these suspended
messages that have already been dealt with.
Thanks
"guest" wrote:
> On Thu, 22 Sep 2005 23:09:01 -0700, Ben wrote:
>
>
> What is state of the orchestration instance and what is the message state?
>
|
|
|
|
|