SQL Processing: efficiency not working for scenarios where the customer tenant does not have a newer carol app version installed

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):
02 - PROBLEM (WHAT'S THE ISSUE?):

Task: https://totvstechfin.carol.ai/tenant51c55f3f6f9d11eb84540a586460016e/carol-ui/tasks/activity/28d1464ba1c04f32b2ec396f25ea34e4?p=1&ps=25&sort=dateUpdated&order=DESC&filters=%5B%7B%22hideInternal%22:%22false%22%7D%5D

It is not enabling the SQL efficiency.

AppName: techfinoffbalance
Pipeline: rskphone
Data Model: rskphone

Pipeline on Unified tenant: https://totvstechfindev.carol.ai/protheusmaisnegunif/carol-ui/pipelines/list/techfinoffbalance/rskphone

Cases impacted: https://console.cloud.google.com/logs/query;query="Error while trying to save pipeline ";cursorTimestamp=2024-01-10T15:24:06.300479120Z;duration=P1D?project=labs-app-mdm-production

I noticed it when enabling the apps “techfinoffbalance“, “techfinmndatasul“ and “winthormaisnegapp“.

https://cloudlogging.app.goo.gl/BQoiZx2oLSMSWb8k8

When the card

deployed in production we had instability in pods of the worker.

https://totvscarol.slack.com/archives/C029SLMQ092/p1707153138221419

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

  1. Carol App released.
  2. Created the unified.
  3. Installed the carol app on unified.
  4. The Tenants don’t have the connection on tenant document pointing to the unified.
    1. This is causing the tenant to do not locate the unified tenant, carol app and pipeline when starting the pipeline.
  5. Generated the SQL Tasks - they are not processing.
The app has several versions.

Most versions have no Unified Tenant defined.

When processing the pipeline Carol is getting the wrong version, that has no unified tenant, generating the error.

We need an app with multiple versions before defining the unified tenant so eventually when running the pipeline Carol will get the version without unified tenant specified.

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):

  • Efficiency working for cases described on above steps.
    • Today impacting some apps related to Techfin, one example are the Mais Negócio apps (Protheus, Datasul, Winthor).

Activity

Automation for Jira 15 February 2024, 12:27 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its PR was just merged into master branch in Github.

Automation for Jira 12 February 2024, 19:44 Jira Internal Users

@MARCOS STUMPF ,
@Gabriel DAmore Marciano , @André Pereira de Oliveira , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Glaucio Scheibel , @Jonathan Willian Moraes , @Renan Schroeder

This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-02-12, 2024-03-04

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

Automation for Jira 12 February 2024, 15:56 Jira Internal Users

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

Douglas Coimbra Lopes 9 February 2024, 17:58 Jira Internal Users

@André Pereira de Oliveira Manual Tests and Regression OK. It is pending only the code review. cc @Gabriel DAmore Marciano

Automation for Jira 9 February 2024, 17:45 Jira Internal Users

Cenario encontrado no .
• ✅ *Update: Topico Resolvido. Issue ja mapeada no card *
• Uma vez atualizado de `true`-> `false` ou o parametro ja em `false` value do parametro `checkExistsDataToProcess,` a otimizacao generica nao esta sendo desativada para o data model mdmpurchaseorder
• Detalhes no card + sandbox

Edited on Slack - platform-internal - Douglas Coimbra Lopes

Automation for Jira 9 February 2024, 17:44 Jira Internal Users

Cenario encontrado no .
• ✅ *Topico Resolvido: Issue ja mapeada no card *
• Uma vez atualizado de `true`-> `false` ou o parametro ja em `false` value do parametro `checkExistsDataToProcess,` a otimizacao generica nao esta sendo desativada para o data model mdmpurchaseorder
• Detalhes no card + sandbox

Edited on Slack - platform-internal - Douglas Coimbra Lopes

Douglas Coimbra Lopes 9 February 2024, 15:21 Jira Internal Users

ORCHESTRATOR SQL PROCESSING (OUT OF ALLOWED LIST)

NO ERRORS ON GCP:

ORCHESTRATOR SQL PROCESSING DOUBLE-CHECKED FOR CUSTOMER TENANTS IN THE ALLOWED LIST

Automation for Jira 9 February 2024, 15:19 Jira Internal Users

🚨 Cenario encontrado no .
• Uma vez atualizado de `true`-> `false` ou o parametro ja em `false` value do parametro `checkExistsDataToProcess,` a otimizacao generica nao esta sendo desativada para o data model mdmpurchaseorder
• Detalhes no card + sandbox

Edited on Slack - platform-internal - Douglas Coimbra Lopes

Automation for Jira 9 February 2024, 15:19 Jira Internal Users

🚨 Cenario encontrado no .
• Uma vez atualizado de `true`-> `false` ou o parametro ja em `false` value do parametro `checkExistsDataToProcess,` a otimizacao generica nao esta sendo desativada para o data model mdmpurchaseorder

Sent by Slack - platform-internal - Douglas Coimbra Lopes

Automation for Jira 8 February 2024, 20:57 Jira Internal Users

Github user olivandre has just commited and issue was sent back to the REVIEW column.

Automation for Jira 8 February 2024, 20:36 Jira Internal Users

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

Automation for Jira 8 February 2024, 19:07 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-5458 Done add cache tenant app from unified tenant

Automation for Jira 7 February 2024, 13:30 Jira Internal Users

@MARCOS STUMPF ,
@Gabriel DAmore Marciano , @André Pereira de Oliveira , @Douglas Coimbra Lopes , @Gabriel DAmore Marciano , @Jonathan Willian Moraes , @Renan Schroeder

This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-02-12

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

Automation for Jira 7 February 2024, 13:30 Jira Internal Users

Message thread link on #red-phone channel:

https://totvscarol.slack.com/archives/C03NT4US9J9/p1707309028472749