Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

LiveRisk-1.5 Release Notes

LiveRisk-1.5 - Release Notes

We’re thrilled to bring you the latest updates to the Live Risk API, focused on smarter configuration, expanded risk monitoring, and better data integrity. This release includes new feature development, key fixes, and enhancements that empower teams to operate with more precision and context across multimodal shipments.

🌟 Key Updates

Risk Calculation and Device Insights

  • Full Schema Validation

    • Enforces strict schema validation on API response objects to prevent contract mismatches and ensure API consistency.

Lane and API Improvements

  • Case-Insensitive Lane ID Matching

    • lane_id and customer_lane_id fields now support case-insensitive matching for greater flexibility.

  • Default Event Location Coordinates

    • When external events lack geopolygons, default coordinates will now use the relevant stop location instead of (0,0).

  • Journey Config Error Handling

    • Logic updated to gracefully handle missing origin/destination fields in journey_config, reducing false error flags for unstructured shipments.

  • Air Event Integration

    • Integration work has begun to add air event feeds, expanding beyond the current geopolitical and weather alert sources.

🕷️ Bug Fixes

  • Foreign Key Mismatch in Live Risk DB

    • Addressing inconsistency between raw and prediction tables due to unexpected record count discrepancies.

    • Does not impact end-user responses but may affect internal metrics.

  • Stop Filtering Visibility

    • Added new field identified_stop_source to differentiate stops auto-detected by Paxafe vs. predefined by customers.

    • Helps explain unanticipated stop entries in reports.

  • Unexpected Contracted Lead Time Display

    • Clarifying how contracted transit time appears in risk summaries for newly added lanes without explicit PTA values.

    • Interim logic uses historical averages + 20% buffer. Future fix will include rounding improvements.

  • API Failure: Value Too Large

    • Fixed error where oversized values triggered PXER500. System now validates request payloads more effectively.

📝 Important Notes

  • Lane ID Case Insensitivity

    • Case-insensitive matching does not yet apply to journey_config references. Use with caution.

  • Contracted Time Logic for New Lanes

    • If no PTA is passed, Live Risk derives thresholds using Average Transit Time + 20% buffer.

  • Schema Enforcement

    • Developers integrating with the API should validate against the official schema spec: v1, v2.

  • Full Live Risk API documentation can be found here.

  • Additional schema fields in external_impact response:

    • "current_cancel_percent"

    • "current_delay_percent"

    • "current_flight_count"

    • "mean_arrival_delay"

    • "mean_departure_delay"

    • "mean_dwell_days”