Proof Issue on Versions 2 or Higher

So weird. We are having a similar issue. Any new proof created is not notifying the original recipient via email. If we use an automated workflow it does not notify the first stage people. We are using the message all method as a workaround as well. After the first stage is completed it does notify the subsequent stages (thank goodness) It doesn’t work if we create a basic proof either.

In all of my investigating several users noticed that notify user check box (that is usually checked as part of our workflows) was now unchecked. But checking it did not solve the messaging issue.

I checked the proofing workflow activity and noticed that where it lists the recipients it says email notifications disabled. But no changes were made recently and when I checked all the places that could influence this we have everything set up correctly.

I do have a support ticket in but this really is causing an issue for our team. Not to mention how much of my day this hijacked. But admittedly it’s these types of mysteries that I most enjoy investigating. I just usually prefer to uncover a solution. Lol

Sadly still not fixed and even worse, I'm not getting the same result that Tracy is where subsequent stages are getting notifications. We still have to do the Message All Proof Reminder emails for all stages.

What we have been doing to help:

• Made sure that Proof Owners are selecting the Decisions email notification type so they get that email when a decision is made. (This is great in case someone forgets to at mention them that it is done)
• Made a Proof Approval Report for all users. (Sadly a bunch of them hate logging in so not sure if it will help too much).

Proof Approval Report Info: (Unfortunately, I will only work if you have documents at the project level like us. If you have it at the task level, project name is too far)

Object Type: Proof Approval

Fields: Project Name*, Document Name, Version, Proof Creator, Document Version Entry Date (which renamed to Upload Date)

Project Name text mode:

displayname=Project

querysort=documentVersion:document:project:name

textmode=true

valuefield=documentVersion:document:project:name

valueformat=HTML

Grouping Text Mode:

group.0.name=

group.0.valuefield=documentVersion:document:project:Portfolio Name

group.0.valueformat=customDataLabelsAsString

textmode=true

Filter Text Mode:

isCurrentDocumentVersion=true

isCurrentDocumentVersion_Mod=eq

approverID=$$USER.ID

approverID_Mod=in

approverDecision=Pending

approverDecision_Mod=cieq

isAwaitingDecision=true

isAwaitingDecision_Mod=eq

documentVersion:entryDate=2021-02-25T00:00:00:000

documentVersion:entryDate_Mod=gt

Hope that is helpful to others who needed to get a large Margarita after work yesterday. ;)

UGH!! We went through what sounds like the very same issue last year. It started in January and had been fixed in late April. But then 20.2 rolled out in May and broke it again. Luckily they knew what had been done to fix it the first time, so the second fix was a little quicker.

I'm waiting to hear back from my project managers if it has come back for us again.

These are my case numbers from last year if they might help at all: 00185005 and 00205308

we have had the same issue but through document proofing, not "ProofHQ" proofing. proof 2 and beyond we need to manually resubmit to all proof approvers. very annoying and time consuming.

We have a lot of guest users and I went into the contacts on the proof side and found that all guest users have had the Default email alert disabled. We have had to manually change those. But it happened the beginning of last week and people stopped getting notifications. And we are on NWE

I just tested this and it is still an issue for us.

Hi all,

I know most of you are in touch with support about this already, but I just wanted to let you know that the support team is working together directly with development team leadership to get to the root cause.

In the meantime, the workaround for the proofs that notifications were not triggered would be to use Message All function after the proof is created using the below instructions.

Workarounds:

1. Create a new Proof entirely (not a new proof version)

2. Go to the Workflow and manually send the email (see screenshot)

Screenshot: https://drop.workfront.com/DOu2Lv2g

Thank you for continuing to update your support tickets, this is something our teams are continuing to address.

Kyna