Subscription Dashboard Bad Request - UI not sending queryId in query-polling request

Description

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

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

@Breno Zipoli Monteiro Papa
02 - PROBLEM (WHAT'S THE ISSUE?):

UI is not sending queryId in one of the query-polling requests that build the Subscription Dashboard

Request made by UI:

curl 'https://totvstechfindev.carol.ai/api-ui/sql-bq/query-polling' \
  -X 'POST' \
  -H 'authority: totvstechfindev.carol.ai' \
  -H 'accept: application/json, text/plain, /' \
  -H 'accept-language: pt,en-US;q=0.9,en;q=0.8' \
  -H 'authorization: xxxxxxx' \
  -H 'content-length: 0' \
  -H 'origin: https://totvstechfindev.carol.ai ' \
  -H 'referer: https://totvstechfindev.carol.ai/hrplatformdev/carol-ui/data-subscription?p=1&ps=200&order=ASC&filters=%5B%7B%22period%22:%5B%22range%22,%222023-11-26T13:35:00.000Z,2023-11-30T13:35:00.000Z%22%5D%7D%5D ' \
  -H 'sec-ch-ua: "Google Chrome";v="119", "Chromium";v="119", "Not?A_Brand";v="24"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "macOS"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36' \
  --compressed

Response:

{
  "type": "about:blank",
  "title": "Bad Request",
  "detail": "'queryId' is a required property",
  "status": 400
}

03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):

Open the Network console in browser and open subscription dashboard on any tenant.
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):

https://totvstechfindev.carol.ai/hrplatformdev/carol-ui/data-subscription
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):

Send the payload so the request can complete.

Activity

Automation for Jira 5 December 2023, 18:55 Jira Internal Users

This issue was automatically transitioned to DONE after being deployed to production on Github.

https://github.com/totvslabs/carol-ui/releases/tag/v4.38.0

Automation for Jira 5 December 2023, 18:55 Jira Internal Users

No associated issue on JIRA TOTVS BRAZIL.

Automation for Jira 5 December 2023, 11:41 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).

Automation for Jira 4 December 2023, 16:18 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 4 December 2023, 16:18 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 4 December 2023, 16:18 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 4 December 2023, 16:18 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 2 December 2023, 14:19 Jira Internal Users

This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp.

Automation for Jira 1 December 2023, 22:58 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Automation for Jira 1 December 2023, 22:56 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

fix: CAPL-5107 Done subscription logs loading

Automation for Jira 30 November 2023, 16:41 Jira Internal Users

@Robson Thanael Poffo ,

@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2023-12-11

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.