Ahh. That thread (among others) was pruned and most of it removed (once threads get over a certain size they can hurt performance).
It could be that the notification points to the old version of the thread which is in an archive area which most people can't access. That actually makes sense since the error says something about permissions.
If you navigate to the new thread and setup a new notification on that thread that should avoid the error.
Hm I never thought about that when pruning huge threads, I could probably get around that though doing so would require a lot more work to prune a single thread.
__________________
Uncertainty is an uncomfortable position.
But certainty is an absurd one.
|