Skip to content

fix(fedex): use keyStatus for top-level package status#26

Merged
WolffRuoff merged 1 commit into
mainfrom
fix/fedex-keystatus
Mar 13, 2026
Merged

fix(fedex): use keyStatus for top-level package status#26
WolffRuoff merged 1 commit into
mainfrom
fix/fedex-keystatus

Conversation

@WolffRuoff
Copy link
Copy Markdown
Owner

Summary

  • The FedEx tracking API response contains both mainStatus and keyStatus at the package level. mainStatus is consistently empty; keyStatus is the correct field (e.g. "Out for delivery", "Delivered").
  • Fixes the status=unknown bug on packages that are out for delivery or in other states, even when individual scan events are parsed correctly.
  • Also adds raw_status to the scheduler scrape log to make future status mapping issues easier to spot.

Test plan

  • make test-scraper passes (179 tests)
  • Verified locally against tracking number 513318591333: before fix status=unknown raw_status='', after fix status=out_for_delivery raw_status='Out for delivery'

🤖 Generated with Claude Code

… status

mainStatus is present in the FedEx API response but is consistently
empty. keyStatus is the correct field (e.g. "Out for delivery").
Falls back to mainStatus in case the field naming changes in future.

Also adds raw_status to the scheduler scrape log for easier debugging.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@WolffRuoff WolffRuoff merged commit 5492d99 into main Mar 13, 2026
5 checks passed
@WolffRuoff WolffRuoff deleted the fix/fedex-keystatus branch March 13, 2026 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant