PRDE - Story default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Douglas Coimbra Lopes

02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):

• The platform is always waiting for the mdmTaskId from responses of the endpoint {{/v1/schema/ {mdmEntityName}

  }}

• Hence, when the Notification Schema Changes task fails due to a 409 error, the task ID is null. This error occurs during the death of a worker pod.
• In order to improve the resiliency of the platform, we should review this endpoint behavior, reading the taskId available on the code instead of reading the endpoint response task.
• GCP: https://cloudlogging.app.goo.gl/XtHosSxhoRzQJZia6
• 
• Thread: https://totvslabs.slack.com/archives/C02C1SARBDH/p1691940151408949
• After the analysis, in Instructions it’s defined what have to be done in this card.

• 03 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
  04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
  05 - WHO CAN USE THIS FEATURE (USER ROLES):
  06 - ACTIVITY DIAGRAM (ACTIVITY DIAGRAM LINK AND IMAGE):
  07 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):
  08 - ALTERNATIVE STEPS:
  09 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
  10 - ACCEPTANCE CRITERIA: