Message step failing as Obsolete (Activity_was_rescheduled) (Doc ID 2956907.1)

Last updated on JULY 10, 2023

Applies to:

Goal

Let's say we have a Manual Message Scenario with a step that is invoked when specific service request is submitted and the business workflow of the technicians assume that they first submit the service request, then start the activity. In this particular business use case, all activities are non-scheduled in tech pools, so OFS will essentially move the job from non-scheduled pool to scheduled/next in route then it will start the activity. If the step is not in final status by the time the technician is moving the activity, the step will fail in Obsolete status with description "Activity was Rescheduled"  

Question:
Is there any tweak we can implement so OFSC can fire the message step even though the activity is changed?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.