Is anyone experiencing the issue, where the email link provided in the communication from a thread response does not work correctly?

Hey Marie.Cassidy ,

I would expect this to happen if the response in the thread has been sent to the abuse queue which effectively removes it from visibility on the site. Have you checked if that's the case?

Have you also looked at the e-mail template for forum replies, if you want to link the person to the thread rather than the reply, then there may be a different token to embed in the e-mail. Though from personal experience I would advise against linking to the general thread rather than the exact reply, depending on the wording in the template users would expect to be linked to the reply that they're notified about.

Thanks Christopher,

So strangely, nothing has changed that I am aware of on the email template for forum replies, unless something changed when there was an update to 12.1.5.27118 

And they are not hitting the abuse queue.

The fact the workaround is to remove the actual thread link to take them to the entire post, is already causing consternation and frustration, so agreed will not be linking to the general thread.

Thanks Christopher,

So strangely, nothing has changed that I am aware of on the email template for forum replies, unless something changed when there was an update to 12.1.5.27118 

And they are not hitting the abuse queue.

The fact the workaround is to remove the actual thread link to take them to the entire post, is already causing consternation and frustration, so agreed will not be linking to the general thread.

Hi Marie.Cassidy 

It seems like there is an issue with the token within the Forum Reply Email Body Template. I would create a ticket with Verint as I see other environments on earlier Verint instances with the same issue - but users are still directed to the thread. 

Administration > Notifications > Forum Reply > Email - Body > Tools > Source Code

Thanks Sara, issue already reported to Verint. Was hoping maybe someone had a workaround.

Hopefully we'll at least see it listed in the known issues log with a TE reference so we can keep track of when it'll be fixed.

Bringing this one back up. There is a confirmed issue, resolved in 13, BUT is there a workaround for Version 12.