title: How to get log entries out of the inner apoc.periodic.iterate statement in Neo4j?
body: <h2>Initial situation</h2>
  
  <p>The <a href="https://neo4j-contrib.github.io/neo4j-apoc-procedures/#log" rel="nofollow noreferrer">log procedures</a> allow us to write values to the log file.
  Run in the Neo4j Browser, the statement <code>Call apoc.log.info('Hello %s', ['Neo4j Community']);</code> immortalizes the greeting under logs/neo4j.log and logs/debug.log as expected.</p>
  
  <p>If I now try to write the same greeting from a <code>apoc.periodic.iterate</code> call into the log, the query itself will be successfully executed and noted in the log, but the desired output will not appear - without an error message.</p>
  
  <pre><code>CALL apoc.periodic.iterate('
      RETURN "reduced single test record"
  ', '
      Call apoc.log.info(\'--&gt; Hello %s\', [\'Neo4j Community\'])
      RETURN true;
  ', {batchSize: 1000, iterateList: true, parallel: true})
      YIELD
          total, committedOperations, failedOperations, batches, failedBatches, retries, errorMessages, batch, operations, wasTerminated;
  </code></pre>
  
  <h2>Target scenario</h2>
  
  <p>How can I get log entries out of the inner <code>apoc.periodic.iterate</code> statement?</p>
  
  <hr>
  
  <h2>Update</h2>
  
  <p>After upgrading to Neo4j 3.5.8, the issue scenario remains unchanged.
  The one-liner output is written correctly to the log (second line), but not from the <code>apoc.periodic.iterate</code> statement, although it is noted in the log itself (line 3 to 8).</p>
  
  <pre><code>2019-07-29 20:11:10.431+0000 INFO [o.n.i.d.DiagnosticsManager] --- SERVER STARTED END ---
  2019-07-29 20:12:37.425+0000 INFO [o.n.k.i.p.Procedures] hello_neo4j_community_from_single_line_statement_
  2019-07-29 20:13:36.179+0000 INFO [o.n.k.i.p.Procedures] starting batching from `
      RETURN "reduced single test record"
  ` operation using iteration `
      Call apoc.log.info('--&gt; Hello %s from inner statement.', ['Neo4j Community'])
      RETURN true;
  ` in separate thread
  </code></pre>