B6027 E-Mail Notifications and subject line changes

Hi Raiy,

Yes. I have the same problem as you.  I get the email notification but the subject does not include the task name and does not include the backup results. The "additional results notification" results options are checked but not implemented.

Program is not acting the way the help file describes it should.

http://www.acronis.com/en-us/support/documentation/ATI2016/#24426.html

Another user also reported the same.

https://forum.acronis.com/forum/104988

===============================

Edit:

A work around illustrated in next posting  or #2 below.

Thanks Jim and Gerhard, To get the task name plus the task results to appear as the email notification subject line, a 2016 workaround necessay.
Applicable to each new or existing 2016 task where task name and results are missing from the subject line--hopefully just this special build where the problem has surfacec.
============================================================

Workaround is

=============================================================
During the task and notification creation, click on the "Show Extended Settigs" and delete all content of the subject line so a greyed out subject line appears. Save the task. See illustration below. It works or at least it does for me. ======================================================================

======================================================================
PS: While I do not recommend editing an existing task, it is possible to edit and delete the subject line as shown above from within an existing task same as when creating a new task notification. =======================================================================
=======================================================================
To save a new task without running a backup during the task save, use this procedure.

Later Edit:

If task edited or changed in any way, the notifificatin fix will need to be redone.  Task editing of any sort discouraged.

Thanks Grover, that certainly seems to solve the problem - why did they ever change it - beats me. Talk about trying to confuse the customer. It worked OK as it was for years and then suddenly they make this change Oh well!

Hey GroverH,

I seem to keep thanking you for helping me fix things with ATIH 2016, this fixed another problem I had after upgrade to latest upgrade version.  Very Much appreciate your complete explanation with illistrations on how to FIX problems...

Seems to be working on all my backup tasks both local and to cloud. Thanks Grover!

I have confirmed that email notifications for successful backup and failed backup do in fact state as such in the subject line like they used to.

Thanks again Grover.

Now my question to the ATI team is, when are you going to release a fix for this bug and the green arrows that don't show up properly in version 6027?

Well it may resolve the issue BUT if you edit the backup task for ANY reason you will have to go and do the same thing again on the e-mail subject line. Previous edits to make it blank get the same text as before after an edit. Sigh!!!

I now have another product and it works MUCH better than ATIH, AND I can make it do what I require so much more flexibility.

Ray,

Yes, if the task is edited for other reasons, you should include the task notification  in your editing (as shown above in post #2) so the edit "options" needs only to be opened once.

Don't forget, editing the task for any reason other than scheduling will usually cause the task to not perform as expected.

My recommendation to keep the task running successfully is not to make any task edits and if edits needed, then start over with a new task with the corrected settings. I realize that "not editing" is not the preferred solution but the "no edit" recomendation is one way of keeping the tasks performing correctly.

This particular problem of the notification subject not including the pass/fail information only appeared in this last update of 2016, build 6027 and hopefully will be fixed in the next build release.

I agree its not usually good practice to edit a working task but sometimes you have to, even so changing something I have NOT changed is just plain WRONG. What else have they changed without my knowledge - sigh.

Their programmers need a good course in programming I am begining to think. At least enhancing their knowledge on what is good and what is bad practice as well as actually TESTING their changes to ensure the change they have made impacts NO other area - regression testing.

Acronis testing IMHO is very poor.

RayG wrote:

I agree its not usually good practice to edit a working task

I understand that philosophy, but by definition Acronis did in fact edit all our working tasks by releasing 6027!!

Yes, and that probably why there has been so many reports of problems and many users had to start over with new task.

While it may be inconvenient, I encourage all users to start over with all new tasks whenever a new version is upgraded. .

But of course, I am expressing my own opinion in an attempt to save others the problems I have encountered. starting over just saves so many problems