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

Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).

feat: CAPL-5180 Done - add logs to explain why we are allowing this task…

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

@Geny Isam Hamud Herrera The card has been validated by the QA team. It is pending only the code review.

cc

🚨 Bug encontrado no
✅ Update Topico resolvido: Cenario ocorre devido Install new versionn + checkout
• Unified processando schedule tasks modelo batch
• Antes da execucao da primeira task, um batch ja constava como READY
1. Scenario: A primeira task roda com Has Batch True, porem apresentando msg de logs de `Forcing executing pipeline since there's a new checkout`
+ `Data to process was not found or not ready`
•
• Taskid: `3b31601628014126b443c41ce85c440b`
• Para maiores detalhes podemos alinhar na meeting de notes agendada para 15h
•

Edited on Slack - platform-internal - Douglas Coimbra Lopes

Em conversa com o Douglas percebemos que a pipeline executou porque a instalação do CarolApp fez um update no documento de Pipeline e na proxima execução após essa instalação de CarolApp a task foi executada como esperado.

🚨 Bug encontrado no
• Unified processando schedule tasks modelo batch
• Antes da execucao da primeira task, um batch ja constava como READY
1. Scenario: A primeira task roda com Has Batch True, porem apresentando msg de logs de `Forcing executing pipeline since there's a new checkout`
+ `Data to process was not found or not ready`
•
• Taskid: `3b31601628014126b443c41ce85c440b`
• Para maiores detalhes podemos alinhar na meeting de notes agendada para 15h
•

Edited on Slack - platform-internal - Douglas Coimbra Lopes

🚨 Bug encontrado no
• Unified processando schedule tasks modelo batch
• Antes da execucao da primeira task, um batch ja constava como READY
1. Scenario: A primeira task roda com Has Batch True, porem apresentando msg de logs de `Forcing executing pipeline since there's a new checkout`
+ `Data to process was not found or not ready`
• Data to process was not found or not ready
•
• Taskid: `3b31601628014126b443c41ce85c440b`
• Para maiores detalhes podemos alinhar na meeting de notes agendada para 15h
•

Edited on Slack - platform-internal - Douglas Coimbra Lopes

🚨 Bug encontrado no
• Unified processando schedule tasks modelo batch
• Antes da execucao da primeira task, um batch ja constava como READY
• Scenario: A primeira task roda com Has Batch True, porem apresentando msg de logs de no data ready.
•
• Taskid: `3b31601628014126b443c41ce85c440b`
• Para maiores detalhes podemos alinhar na meeting de notes agendada para 15h
•

Sent by Slack - platform-internal - Douglas Coimbra Lopes

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

feat: CAPL-5180 Done - add logs to explain why we are allowing this task…

This issue was automatically transitioned to IN PROGRESS, as its branch was just created in Github.

CAPL-5180-logs-efficiency

@Robson Thanael Poffo ,

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

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

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