fluent-bit: [1.7rc3] Missing log message when retry succeeded

Bug Report

Describe the bug Sometimes a chunk can’t be delivered and fluent-bit is retrying it. When that retry succeeds in 1.6.10, I receive a message like this:

[ info] [engine] flush chunk '1-1612248354.875642810.flb' succeeded at retry 1: task_id=1, input=forward.3 > output=syslog.0

In 1.7rc3 (I use the fluent/fluent-bit:1.7.0-rc3 docker image) this message is not there anymore.

To Reproduce

• Create a pipeline where the output talks to another process, for example syslog
• Turn off the output consuming process
• Send messages
• Turn on the output consuming process

Expected behavior If a chunk was successfully retried, I except in the logs

[ info] [engine] flush chunk '1-1612248354.875642810.flb' succeeded at retry 1: task_id=1, input=forward.3 > output=syslog.0

Your Environment

• Version used: fluent/fluent-bit:1.7.0-rc3 docker image
• Configuration: Input fluentd via tcp, output syslog
• Environment name and version (e.g. Kubernetes? What version?): Just playing with containers on my local machine
• Server type and version: Laptop 😄
• Operating System and version: Debian Stable
• Filters and plugins:

Additional context When I do turn off the output processing process and turn it on again, there is always one chunk stuck. That log message made watcihing the process easier. Now I use the CONT signal. For that issue I will try to create a minimal example and create another bug.