Routing to Unscheduled Bucket/Technician
SummaryRecurring Routing to push activities to buckets as "unscheduled"
We currently create all activities to a "master" bucket. The bucket runs a recurring routing plan to push activities to children buckets(managers), and each child bucket has recurring routing to children resources(technicians).
Every "add/move" triggers a message scenario to "unschedule" the activity assigned to a bucket. The managers then manually run routing to assign the activities to technicians.
We are experiencing issues with routing activities that are linked to activities already routed to children buckets and "unscheduled".
This appears to be due to routing to the current date and time, when the linked activity is unscheduled.