DNR async option

phenom

Here is what I found in the docs for OD 7.1 Deploy Config Guide

async - indicate whether or not to run the script asynchronously. The output from scripts run asynchronously is not captured. Default value is no.

Does this mean that the DNR info is logged when the async is set to no? I have tried this but the DNR info is not getting logged within the OD logs on the sender. Did anybody try this successfully?

Adam Stoller

Here is what I found in the docs for OD 7.1 Deploy Config Guide async - indicate whether or not to run the script asynchronously. The output from scripts run asynchronously is not captured. Default value is no. Does this mean that the DNR info is logged when the async is set to no? I have tried this but the DNR info is not getting logged within the OD logs on the sender. Did anybody try this successfully?

I believe the "output" being referred to is the XML snippet one sends from a DNR to indicate the DNR failed so that OD rolls back. If you're running the DNR asynchronously, OD will not be looking for a failure indicator from the DNR.

To the best of my knowledge any other output from DNRs is silently ignored - regardless of the setting of async.