They should automatically redirect, but we've discovered that they don't always.

When we have members of the public visiting 'old links' or 'redirected links' on some occasions they get stuck and encounter a 404/500 error. This may particularly be with content that was moved from a 'secret' or 'private' group to a public one, but it happens anyway. I haven't quite been able to pin it down.

It may also be the case that if the person has javascript disabled (because of course people are privacy paranoid), it may not always redirect properly.

I recommend trialling it under various scenarios in a staging environment before trusting a public, production instance.

We setup a redirect in the cdn/web access to also compensate for when the platform doesn't redirect properly, using re-write maps, and functionality in akamai. We haven't been able to trust Verint completely for redirects.

They should automatically redirect, but we've discovered that they don't always.

When we have members of the public visiting 'old links' or 'redirected links' on some occasions they get stuck and encounter a 404/500 error. This may particularly be with content that was moved from a 'secret' or 'private' group to a public one, but it happens anyway. I haven't quite been able to pin it down.

It may also be the case that if the person has javascript disabled (because of course people are privacy paranoid), it may not always redirect properly.

I recommend trialling it under various scenarios in a staging environment before trusting a public, production instance.

We setup a redirect in the cdn/web access to also compensate for when the platform doesn't redirect properly, using re-write maps, and functionality in akamai. We haven't been able to trust Verint completely for redirects.

Interesting. Group Type is the same between the 2 parent groups. We are just getting the following error: