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

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

@Cindy de Araujo Soares Moore
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

After the changes in

(deployed on September 11th) we still see a staging schema stuck in CHANGE_IN_PROGRESS.

Error to update the schema status → https://cloudlogging.app.goo.gl/sVbSVwNvRrhm7n8T9

The error above was thrown in this line: https://github.com/totvslabs/mdm/blob/master/mdm-tasks/src/main/java/com/totvslabs/mdm/task/BigQuerySchemaChangedNotificationProcessor.java#L174-L175

Check data model and schemas stuck in CHANGE_IN_PROGRESS after the deployment of September 11th.

Schemas → [http://localhost:19201//mdmStagingSchema/_search?q=(mdmBigQuerySynchronizationStatus:CHANGE_IN_PROGRESS AND mdmLastUpdated:[2023-09-11T17:55:47.165Z TO *])|http://localhost:19201//mdmStagingSchema/_search?q=(mdmBigQuerySynchronizationStatus:CHANGE_IN_PROGRESS%20AND%20mdmLastUpdated:%5B2023-09-11T17:55:47.165Z%20TO%20*%5D)]

Data models → [http://localhost:19201//mdmEntityTemplate/_search?q=(mdmBigQuerySynchronizationStatus:CHANGE_IN_PROGRESS AND mdmLastUpdated:[2023-09-11T17:55:47.165Z TO *])|http://localhost:19201//mdmEntityTemplate/_search?q=(mdmBigQuerySynchronizationStatus:CHANGE_IN_PROGRESS%20AND%20mdmLastUpdated:%5B2023-09-11T17:55:47.165Z%20TO%20*%5D)]

03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:

---

CAPL - Bug default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - PROBLEM (WHAT'S THE ISSUE?):
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):