Normally sending email should not take long. If the system is configured properly and email server can be always reached, sending email should take just a fraction of a second, which makes irrelevant how this is being run, async or sync.
If you run script type jobs you can do all error catching and handling yourself using OnError... statements. In this case you have full control when and how to email to trigger another job. You can do MailSend, trigger another job using JobRun and many other things BTW: Notification processes should be used for simple user notifications or job semaphoring only. They should be set to run quick and easy. : Greetings all,
: I've read in the forums that while any task can be set to asynchronous, if
: you select to be notified on error, the notification proces (sending of an
: email) will not be asynchronous. Can I get around this by triggering a
: separate job on error which only sends an email, and setting this job to
: asynchronous?
: If this won't work, how can I notify on error and keep everything truly
: asynchronous?
: If thiw will work, how can I catch the error message so that I can use it in
: the subject/body of the email I send in this new task?
: Thanks for any help!
: Ryan
|
