Well, IMO, you’re violating modularity and segregation principles. What you’re doing is akin to a class method knowing the name of the variable used by the code that calls the method. In structured programming, that is a distinct no-no.
Perhaps logging the pipeline will do what you’re after. You can do this:
Create your own FLOW service. Named perhaps “logMyPipeline”.
Set the “Enable auditing” and “Include pipeline” properties for that service to “Always”
Within it, call pub.prt.log:logActivityMessages (assuming you have PRT/PE).
Call it from your “parent” service. Passing whatever makes sense for FullMessage/BriefMessage (nothing is okay).
This will log everything in the pipeline. Then you can use MWS to review the audit log and pipeline.
Another alternative – have the caller pass the name of the var. Then the logging will use the name you want. A maintenance headache of sorts (if anyone changes the var name, they have to remember to change the static input too – but that should be rare).