Skip to content
This repository was archived by the owner on Nov 13, 2023. It is now read-only.
This repository was archived by the owner on Nov 13, 2023. It is now read-only.

500 status code should not be considered as transient error #32

@BDavidRamesh

Description

@BDavidRamesh

Current Problem Statement:
the current 5XX check includes 500 which is not TransientError,
500 error requires code changes or query changes by the dev team.

  1. so retry for 500 always returns 500
  2. if there is dependency on Service-1 for 3 different Api calls for 3 different workflows, opening circuit for 500 error on Api-1 makes the entire Service unavailable.

Proposed Fix:
response status code should be ">500" instead of ">=500"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions