Articles in this section

Track & Trace Gateway Active/History Issue Tracking

Profit Tools Admin
  • Updated

This article is intended for customer tracking of active and resolved Track & Trace Gateway-related tracing issues. 

 

Active tracing-related issues:

(Updated 11.29.23)

M.I.T. Seagirt

  • Issue Active
  • Behavior: Discharge prompted not relative to final destination
  • Actions Taken: Development ticket submitted for review

Global Container Terminal

  • Issue Active
  • Behavior: Active Container information not being reported. 
  • Actions Taken: Notification to Data Provider 

History Resolved Issues:

(Updated 11.29.23)

Resolved in Track & Trace Gateway Version 5.0.209

Husky Terminal 

  • Issue Resolved
  • Behavior: Husky Failure to Trace 

Resolved in Track & Trace Gateway Version 5.0.209

Bayport/Barbours Cut 

  • Issue Resolved
  • Behavior: Failure to trace

 

(Updated 11.14.23)

 

Fenix Marine Services (FMS): Resolved

  • Issue Active
  • Behavior: Discharge not populating
  • Actions Taken: Development ticket created for investigation of resolution. Discharge is not explicitly defined by Terminal API. Requested Terminal add data to API. Will Add information when provided by Data Provider

 

Everport Issue Status: Resolved

  • Behavior: Everport Traces failing due to increased CAPTCHA prompting during terminal site login
  • Actions Taken: Profit Tools Development ticket created for the implementation of resolution.
  • Resolution: Trace converted to eModal API for returned data

Trapac 

Ports of America Outtage (PNCT, Seagirt, WBCT)

  • Issue Resolved
  • Behavior: Failure to trace PNCT, WBCT, and MIT Seagirt terminal due to Ports of America API Outtage
  • Resolution: Issue resolved by Dataprovider

Trapac 

  • Issue Status: Resolved
  • Behavior: Trapac Terminals availability status not changing to Available = 'YES' when the container is fully released and available for pickup
  • Resolution: Issue resolved by Profit Tools development team

CSX (Rail)

  • Issue Resolved
  • Behavior: CSX LFD not being generated due to ETA not being reported for CSX Containers that directly effects the interval in which a container is traced to be able to retrieve notifying events that would generate LFD. 
  • Resolution: Issue resolved by data provider

 

  • Issue Status: Resolved
  • Behavior: Trace Failure for Trapac Terminals due to Trapac API Outage
  • Resolution: Data Provider correction issue

(Updated 1.16.23)

 Fenix Marine Terminals (FMS)

  • Issue Status: Resolved
  • Behavior:  FMS tracing failing due possible issue with FMS API Service
  • Resolution: Resolved

BNSF

  • Status: Resolved
  • Behavior: Last Free Day not reported in some cases for BNSF containers with active availability. 
  • Actions Taken: BNSF Contacted regarding Last Free Day data not being reported VIA direct Rail API.

Ports America Terminals

(Updated 9.2.22)

  • Status: Resolved
  • Behavior: Ports America terminals not reporting Release Status as Data Provider API does not explicitly report Released. (PNCT, WBCT, MIT Seagirt)
  • Resolution: If No Holds are present for a container a release status will be reported comparative to the terminal Ports America website. 

Ports America Terminals

(Updated 9.2.22)

  • Status: Resolved
  • Behavior: Failure to trace availability for Ports America Terminals (PNCT, WBCT, MIT Seagirt)
  • Resolution: Direct connection made to Ports America API for container availability retrieval

New York Terminal (NYC)

(Updated 5.18.22)

  • Status: Resolved
  • Behavior: Current Active Container information not reported by eModal EDS API Platform where information is projected on eModal ECP (Web) portal
  • Resolution: Resolved with Data Provider

Trapac Terminals: 

(Updated 8.18.22)

  • Status: Resolved
  • Behavior: Failure to trace availability for Trapac Terminals
  • Resolution: Data Provider restored connection
    • Note: Due to new OSRA Regulations Terminal will not provide LFD/Demurrage in data content

Canadian Rail Pacific (CPR)

(Updated 8.18.22)

  • Status: Resolved
  • Behavior: Last Free Day not being generated in some instances where Data Provider reporting the last event out of order faulting generation of Last Free Day
  • Resolution: Data Provider resolved data reported

CSX

(Updated 8.18.22)

  • Status: Resolved
  • Behavior: Last Free Day not being generated in some instances where Data Provider reporting the last event out of order faulting generation of Last Free Day
  • Resolution: Data Provider resolved data discrepancy

Global Container Terminal (GCT)

(Updated 8.5.22)

 

  • Status: Resolved
  • Behavior: Current Active Container information not reported by eModal EDS API Platform where information is projected on eModal ECP (Web) portal
  • Resolution: Data Provider Resolved

New York Terminal (NYC)

(Updated 8.5.22)

  • Status: Resolved
  • Behavior: Current Active Container information not reported by eModal EDS API Platform where information is projected on eModal ECP (Web) portal
  • Resolution: Data Provider Resolved

 

Trapac B136

(Updated 6.20.22)

  • Status: Development Ticket submitted for investigation
  • Behavior: Trapac B136 container not reporting availability
  • Resolution - Converted Trapac to Direct API with Terminal

Long Beach Container Terminal (LBCT)

(Updated 6.20.22)

  • Status: Resolved
  • Behavior: LBCT containers not reporting availability
  • Resolution - Terminal corrected API Key Access Permissions

APM

(Updated 5.6.22)

  • Status: Resolved
  • Behavior: Lapse in APM API connectivity causing failure of trace.

Track & Trace Gateway

(Updated 5.6.22)

  • Status: Resolved
  • Behavior: Multiple Track & Trace Gateway instances tracing a single unique eModal container would result in a single instance receiving information.

Global Container Terminal

(Updated 1.21.22)

  • Status: Resolved 
  • Behavior: Occasional old trip data being reported for containers when current transit has not started, the old data is being reported as most current. 
  • Resolution: Data older than 45 days excluded from returned information

APM VIT: 

(Update 1.21.22)

  • Status: Data Provider contacted regarding availability of LFD information

    • Update: Profit Tools under advisement from data provider Terminal has added Last Free Day to container retrievable data. 
  • Behavior: APM VIT is not reporting LFD for container with active availability

 

SCSPA: 

(Updated 1.18.2022)

  • Status: Terminal is prematurely reporting Available status VIA to data provider. Data Provider is working with terminal EDI team to correct reporting. 
    • Update : Terminal has advised premature report of available status part of terminal for customer scheduling pickup
  • Behavior: SCSPA containers reported container availability when container still actively on vessel transiting

 

1.24.22

Washington United:

(Updated 1.18.2022)

  • Status: Resolved
    • Update: Under advisement from Data Provider, Washington United will implementing addition of Last Free Day in Received information
  • Behavior: Washington United not reporting LFD for container with active availability

1.18.2022

Canadian Pacific Rail (CPR): 

  • Status: Resolved
    • CPR has implemented fix to resolve missed Last Free Day Reporting
  • Behavior: ETA date being surpassed with no LFD reported

CSX: 

  • Status: Resolved
  • Behavior: CSX calculation not reflecting open terminal for New Years Eve/New Years Day. 

 

12.17.2021

Emodal Traced sites:

  • Status: Resolved
    • Containers will update post 12/17/2021 retrieved data pre 12/17/2021 will not update. 
  • Behavior: Container Available but not reporting LFD information

12.14.2021

APM Tracing outage

  • Status: Resolved
  • Behavior: APM containers traced VIA APM API failing to return results
  • Issue: APM Access revoked

12.07.2021-12.8.2021

Amazon AWS System Outage 

  • Status: Resolved - Amazon services restored
    • May require Terminal/Rail sites to be reactivated within Track & Trace Gateway
      • Resolution - Reactivate disabled terminal/rail sites within Track & Trace
  • Behavior: Track & Trace Gateway Platform failing to return results for Terminal/Rails
  • Issue: Amazon AWS outage

11.29.2021

APM VIT Trace Failure

  • Status: Resolved - APM VIT redirected to Emodal API
  • Behavior: APM VIT traces failing
  • Issue: Propass previously used for APM VIT tracing enabled CAPTCHA site security causing inability to retrieve data from site

 

 

 

Related articles