Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Archive and Purge Journey Data Process - How to archive only expired tasks?

Summary:

Our purpose is to archive only expired journeys, without archiving active journeys containing expired tasks and mandatory tasks

Content (please ensure you mask any confidential information):

When we perform the scheduled process of Archive and Purge Journey Data we manage to mass archive expired journeys and tasks; but we noticed that some active journeys, containing a sequence of tasks, get archived as well.

In these sequences of tasks, there are completed "initial" tasks, followed by an expired task and then mandatory tasks (something like completed task → completed task → expired task → mandatory task → mandatory task), which shouldn't be archived. We think that the expired task in the journey "triggers" the archiving process, but how can we prevent the archiving of the whole journey to happen?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!