You will need to monitor the failures on your end internally and notify FedEx Helpdesk if failures persist.

Retry limitations:

• Retry Mechanism (retry to push event data) occurs only when FedEx does not receive 200 or 202 HTTP status code in response from the destination URL. The retry attempts are made over a span of 15 minutes at 5-minute intervals 3 times over 15 minutes (see retry diagram).
• Each time FedEx tries to deliver the event data and receives anything other than 200 or 202, then that transaction will be considered a failure.
• Every event in the case of a failure will be retried 3 times over 15 minutes with 5-minute intervals in between each retry. If all of those retries fail, then the event will be pushed to a missed events queue which you can retrieve from using the retry mechanism on your Advanced Integrated Visibility webhook project. All failed events that have the following HTTPS series values will be stored for 7 days and can be retrieved by initiating the retry process on your Advanced Integrated Visibility webhook project:
  • 200 - Null
  • 400 - ClientID does not match
  • 401- Data Works token is not valid
  • 500 – Null
  Any missed events in those 7 days will be sent to the subscribed destination URL

Retry logic:

Every event in the case of a failure will be retried 3 times over 15 minutes with 5-minute intervals in between each retry. If after all of those retries fail, then the event will be pushed to a missed events queue which you can retrieve from using the retry mechanism on your Advanced Integrated Visibility webhook project.

• Retry logic:
  • Attempt 1:
    Example: Tracking number 823497234824 is 'Delivered', Client sent 400 response. (Anything other than HTTP status 200/202 is considered failure). In this case, we call attempt 1 as failure.
    • Attempt 2 - 1min +/ jitter - Retry 1
    • Attempt 3 - 2min +/ jitter - Retry 2
    • Attempt 4 - 4min +/ jitter - Retry 3

    If FedEx receives a successful response like an HTTP status 200 & 202 for any of the retry requests, then FedEx will stop the retry mechanism for a given event.

Important Points to Note:

• Retry Mechanism (retry to push event data) occurs only when FedEx does not receive 200 or 202 HTTP status code in response from the destination URL.
• Each time FedEx tries to deliver the event data and receives anything other than 200 or 202, then that transaction will be considered a failure.
• FedEx will continue to push new event(s) data if they happen while retrying for the original event.
• FedEx will also push for subsequent events happening thereafter for that Advanced Integrated Visibility webhook.