Skip to content
Load Agent

Driver arrives before follow up cancels ETA ask

← All scenarios

The driver reaches the pickup before the follow-up; the ETA ask is cancelled, nobody is chased.

Client A dry van Do nothingTimers eval passes
Load 481207: Riverbend Foods, 2 stops, 3 contacts

Stops

  1. Riverbend plant (pickup)
    Oct 13, 6:00 AM PDT to Oct 13, 2:00 PM PDT
  2. Valley DC (delivery)
    Oct 14, 9:30 AM PDT

Contacts

  • driver drv_20931 sms
  • dispatcher dsp_4410 email
  • broker brk_0087 email, slack
  1. 7:01 AM Step 1 of 5

    Delay risk high: SMS the driver for the ETA

    matches the eval

    In

    Location ping: delay risk high for stop 1

    Decide

    SOP client_a/delay_risk_high@v1

    followed client_a/delay_risk_high@v1

    No model call 2 delivery outcomes recorded

    Out

    SMS to driver
    Load 481207: what is your ETA to Riverbend plant? Please reply with the time.
    step 1 of ask:eta_request:ping_0700481207/ask:eta_request:ping_0700/1/send_sms
    Timer set for 7:31 AM PDT481207/ask:eta_request:ping_0700/1/set_timer
    Asks after this step 1 open
    • ETA requestOpen
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      7:31 AM
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  2. 7:10 AM Step 2 of 5

    The driver arrives at the pickup: the ETA ask is cancelled

    matches the eval

    In

    Stop statusstop_0710

    Decide

    SOP standard/arrived_at_pickup@v1

    followed standard/arrived_at_pickup@v1; arrived at the stop, 1 ask(s) closed

    No model call 2 delivery outcomes recorded

    Out

    TMS note to TMS
    Load 481207: the driver arrived at the pickup Riverbend plant.
    481207/evt:stop_0710/tms_note
    Timer cancelled481207/ask:eta_request:ping_0700/1/cancel_timer
    Asks after this step 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      arrived at the stop
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  3. 7:31 AM Step 3 of 5

    The follow-up timer was cancelled: nothing fires

    matches the eval

    In

    Clock tick: no timer was due

    Out

    Agent did nothing (correct) Nothing reached the agent, so nothing was sent and no model was called.
    Asks after this step 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      arrived at the stop
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  4. 7:32 AM Step 4 of 5

    A copy of the attempt 1 timer is delivered anyway: dropped by the filter

    matches the eval

    In

    Timer fired: ask:eta_request:ping_0700 attempt 1

    Decide

    Filtered

    timer tmr:481207:ask:eta_request:ping_0700:1 is stale: the ask is closed or already past that step

    No model call

    Out

    Agent did nothing (correct) No message, no task, no timer.
    Asks after this step 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      arrived at the stop
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  5. 8:01 AM Step 5 of 5

    Still nothing: no dispatcher email, no Hero task

    matches the eval

    In

    Clock tick: no timer was due

    Out

    Agent did nothing (correct) Nothing reached the agent, so nothing was sent and no model was called.
    Asks after this step 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      arrived at the stop
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
Prepared for Freight Hero by Marcus Caum Source on GitHub