How do I suspend an activity as a dispatcher?

When resources must return to activities at a later time and they don't want to cancel the activity, they can suspend it. If necessary, you can suspend the activity on the resource’s behalf.

Suspending an activity captures the time that a resource has already spent working on it. It also creates a duplicate activity that the resource can start later, typically on the same day.

You can suspend only started or pending activities. The application behavior on activity suspension:

Action	Application Behavior
Suspend a started activity	Original is marked suspended; a duplicate is created as pending and not ordered
Suspend a pending activity	Activity is converted to pending and not ordered
Multiple suspensions	Most recent suspension duration is considered
Rescheduling suspended activity	Must be done manually; can be moved to a future day

1. Navigate to the Dispatch Console from the navigation menu.
2. In the Resource Tree, select the resource for whom you want to suspend the activity.
3. Select a started or pending activity that you want to suspend.
4. In the activity hint, click Suspend.
   The Suspend activity dialog box displays.
5. Change the Suspension Time as required within the same working day.
   • The time appears in your configured time display format.
   • You can adjust the time in five-minute increments.
   • This time is reflected in the Dispatch Console, Activity History, and sent to external applications if integrated.
   • If you're offline, you must switch to online to change the suspension time.
   • When you suspend a started activity, a duplicate activity is created in suspended status.
   • When you suspend a pending activity, it's converted into a not-ordered pending activity.
   Note: Although the suspension feature is primarily intended for completing activities later on the same day, it can also b used to resume work on future days. In such cases, a mobile worker or dispatcher can suspend the activity and then manually reschedule the duplicate to the next day. This approach allows the same mobile worker to continue the task without creating a new activity through integrations. It's often preferred whe the same person must complete the activity, when avoiding the use of middleware or external systems is desirable, or when there's a need to track work across multiple days. In such cases, the duplicate activity must also be manually moved into a future time slot on the route to ensure it's correctly scheduled.
6. In the Work Area, the current part of the activity closes. It now displays as a suspended activity (scheduled, but not ordered) in the lower half of the page.
   
   
   Note: Alternatively, if an activity can't be completed on the same day, you can mark it as Not Done instead of suspending it. In this case, the mobile worker selects Not Done and chooses a relevant reason, such as Reschedule for tomorrow. This action can trigger an outbound event to the host application, which can then create a new activity for the desired date. This approach might be preferable when rescheduling requires additional approval or control, when assignment rules need to be recalculated, or when existing integrations are already designed to handle incomplete work.
7. Select the Reason for suspension and add notes, if needed.
8. In the Duration field, specify the time needed to complete the remaining part of the activity. If you suspend an activity multiple times, only the duration from the latest suspension is used.
   Note: If your upstream application - such as payroll or billing - needs to calculate the total time worked on an activity, it must aggregate the durations reported across multiple events. When an activity is suspended, the suspended event sends the duration already worked to the upstream application. Later, when the activity is completed, the complete event sends the duration of the final segment. To determine the total time spent - such as 30 minutes on Day 1 plus 60 minutes on Day 2 for a total of 90 minutes - the upstream application must add these values. The Oracle Fusion Field Service itself doesn't automatically combine durations across multiple segments, so this calculation must be handled externally.
9. Click Submit.