AIF – How to get a better error message and stack trace for a failed document?

26 Aug

How many times when working with AIF you got an error and have no idea what caused the issue. The document fails for many reasons and what you get is a very generic error message. Debugging AIF is a painful process and time consuming. Below is the trick that we can find out more descriptive error message and even a stack trace.



Run the job below and replace the GUID with the GUID from the document that failed

static void TestOutboundMessage(Args _args)
    guid id = str2guid("{BCE9B13D-3F3C-497F-A566-55606C3F19B4}");
    AifQueueManager document;

    select firstOnly document where document.MessageId == id;

    // This static method is declared as private and this trick is to avoid changing the access specifier on the class
    new SysDictClass(classNum(AifOutboundProcessingService)).callStatic('processAsUser', [document.MessageId]);


Refresh and review the error again, you will see a more descriptive message and a stack trace that can save your life.


Leave a comment

Posted by on August 26, 2014 in Development


Tags: , , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: