Fill gaps from assistant conversations: clarify LFD priority and rail-only events - #317
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
PR author is in the excluded authors list. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Address two recurring points of confusion surfaced by recent assistant conversations: how the coalesced
pickup_lfdfield is derived, and why certain inland-destination events only appear for rail moves.Changes
webhooks/use-cases/lfd-alerts.mdx: add a "Howpickup_lfdis chosen" section spelling out the fixed line → terminal → rail priority, and clarify that callers who need the earliest date must compareimport_deadlines.*themselves. Replace the earlier ambiguous "the earlier date is the one that matters" wording.webhooks/event-catalog.mdx: tighten thecontainer.pickup_lfd.changeddescription to state the priority order and link to the guide; note thatcontainer.transport.arrived_at_inland_destinationand itsestimated.*counterpart fire only for shipments with an inland rail leg, and link to the rail integration guide.Context
Assistant threads showed users asking whether
pickup_lfdfollows recency or picks the earlier date, and asking why the inland-destination events were not visible or delivered on their accounts. The docs previously implied both priority and "earlier date wins" for LFD, and did not flag the inland-destination events as rail-only.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.