Builds displaying "downstreamPipelineTriggerRunListener" when not configured to do so

Seeing the following message appear in some jenkins jobs.  In many cases, the jobs are not doing any "withMaven" steps (ex: npm builds).  The task is using up an executor on the master node and with >60s duration, is using up too many resources.  The job will show the build is complete, but the console log output will keep spinning until this message appears.

[withMaven] downstreamPipelineTriggerRunListener - completed in 60330 ms

My jenkins system is air-gapped and I am unable to provide logs (only re-typed snippets)