Expand my Community achievements bar.

SOLVED

Starting new Workflow results in SegmentNotFoundException

Avatar

Level 2

We're seeing a recurring issue in Author (AEM 6, SP2, Oak 1.0.11) when a new workflow is started on a resource it fails and spits out an exception. This seems to happen every couple of days. Previously we've been able to run TarMK online compaction, but today that does not seem to be helping. It doesn't matter what workflow it is, Request for Activation, Request for Deactivation, DAM Asset Update, etc. All workflows return an error similar to the log snippet attached. Any ideas on how to resolve this and prevent it from happening again would be appreciated.

1 Accepted Solution

Avatar

Correct answer by
Employee

Is this on a brand new instance? Please set up a brand new instance and then install your projects alone and see if this issue is coming up. Also please raise a ticket at https://helpx.adobe.com/marketing-cloud/contact-support.html

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

Is this on a brand new instance? Please set up a brand new instance and then install your projects alone and see if this issue is coming up. Also please raise a ticket at https://helpx.adobe.com/marketing-cloud/contact-support.html