Skip to content

Stale ping is ignored

← All scenarios

A late low ping recorded before the high ping changes nothing.

Client A dry van Do nothing 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 2

    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 2

    A ping recorded at 6:40 AM (low) arrives late: ignored, risk stays high

    matches the eval

    In

    Location ping: delay risk low for stop 1

    Decide

    Filtered

    no delay risk band change and no stage change, nothing to do

    No model call

    Out

    Agent did nothing (correct) No message, no task, no 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
Prepared for Freight Hero by Marcus Caum Source on GitHub