Closed loicmathieu closed 4 days ago
Revert the ErrorMessage and fetch error logs instead.
The design of the error widget must be improved, I'll open a followup issue for that.
Example from a flow failing on a task (note that there is another log prior the failing task):
Example from a concurrency limit exceeded:
Example flow with the usage of the new errorLogs() Pebble function:
errorLogs()
id: fail namespace: company.team tasks: - id: fail type: io.kestra.plugin.core.execution.Fail errors: - id: errorLogs type: io.kestra.plugin.core.log.Log message: | {%- for log in errorLogs() -%} - task: {{ log.taskId }}, message: {{ log.message }} {%- endfor -%}
Failed conditions 78.9% Coverage on New Code (required ≥ 80%)
See analysis details on SonarQube Cloud
Revert the ErrorMessage and fetch error logs instead.
The design of the error widget must be improved, I'll open a followup issue for that.
Example from a flow failing on a task (note that there is another log prior the failing task):
Example from a concurrency limit exceeded:
Example flow with the usage of the new
errorLogs()
Pebble function: