Determining Workflow Task Error Handler Criteria Values

asked on August 15, 2022 • Show version history

The help documentation doesn't go into a lot of detail about how the different criteria for an error is actually determined by the Workflow Task Error Handlers and I was wondering if we could get some more clarification on the 3 parts.

As an example, I am receiving the following error in my terminated workflow email notification from one of my Workflow servers. I can see the message and within the message I can see what appears to be an error code.

ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]The OLE DB provider "XXXXXX" for linked server "XXXXX" does not contain the table ""XXXX"."dbo"."XXXX"". The table either does not exist or the current user does not have permissions on that table. [XXXXX]

What is the proper way to determine the error code and error type for this message? I imagine most of this information can be gathered from the Error Logs in the Workflow Administration Console, but I'm just looking for confirmation on where exactly.

Along with this, there appears to be a 255 character limit when entering the error message. What is the best way to get around this limitation so those longer messages can be entered?

0 0

replied on August 15, 2022

I've only ever specified error codes in handlers for LFSOExceptions.

As you mentioned, that information can be gathered from the Error Logs, but not everything will report an ErrorCode and it looks like that's mostly only useful for LF errors.

The Exception Type is what should match up with the Error Type in the handler, but I usually don't bother with that either since that's still text comparison and the message is more specific.

As for the error message, I've always just pasted whatever fit and it seems to work so it may be looking for "contains" or "starts with" rather than "equals" when it checks the handler.

0 0

View 4 previous replies

replied on August 15, 2022

That is interesting that partial messages works for you. I entered a partial one on Friday and this morning found out it didn't catch those ones.

0 0

replied on August 15, 2022

Interesting. Where did you copy the error message from? Maybe it doesn't actually use partial matches but my actual error messages were also truncated.

0 0

replied on August 15, 2022

I copied it directly from the error message section of the error in the Error Logs.

0 0

replied on August 15, 2022

I guess we'll have to wait to see what response you get from LF. It's been a long time since I set up any new error handlers so there may be something I else I did that forgot about.

0 0

replied on August 17, 2022 • Show version history

Jason, what version of Workflow are you using? We are currently on 10.4.2.246. Just wondering if it might be a difference in how different versions handle it.

Also, why do you select the "Critical Error" box?

0 0

replied on August 17, 2022

We're on 11 now, but I set those up at least as far back as 10.1, maybe earlier.

I select Critical Error because if it fails all the retries for those particular errors I want it to throw an error rather than a warning so the workflow terminates or a try-catch is triggered.

0 0

replied on August 24, 2022

@████████, are you able to shed some light on this for me?

0 0

Question

Question

Determining Workflow Task Error Handler Criteria Values

Replies

Sign in to reply to this post.