'SecResponseBodyAccess Off' does not prevent response body from being logged (SecRuleEngine == DetectionOnly)

Hi!
Setting SecResponseBodyAccess to Off does not prevent response body from being logged ( SecAuditLogParts ABIJDEFHZ)

Does it mean that with SecResponseBodyAccess Off ResponseBody is still being intercepted?

Expected behaviour - according to https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-(v2.x)#SecAuditLogParts "E: Intermediary response body (present only if ModSecurity is configured to intercept response bodies... Intercepting response bodies requires SecResponseBodyAccess to be enabled"

Server:

• ModSecurity version: ModSecurity v3.0.4
• WebServer: nginx-1.18.0
• OS (and distro): Ubuntu 16.04

Rule Set :
https://github.com/coreruleset/coreruleset/archive/v3.3.0.tar.gz

Additional context
SecRuleEngine == DetectionOnly and SecAuditLogType == Concurrent
Removing E from SecAuditLogParts do prevent ResponseBody from being logged.
If I set SecRuleEngine to On and turn on DEBUG logging - logs do confirm that SecResponseBodyAccess is not ignored (https://github.com/SpiderLabs/ModSecurity/commit/42a472adbda21e6ecc4711fd37d704cdb3d98fbb):
Response body is disabled, returning... 1