Currently we pass the `activation_id` as part of `/run` call to any action runtime [1]. Would it be fine to also pass the `TransactionId` such that it can be accessed by action code?
One usecase of this would be to enable tracing a sequence/composition by linking all activations which are part of same transaction in epsagon [2] Chetan Mehrotra [1] https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#activation [2] https://epsagon.com/blog/epsagon-makes-troubleshooting-apache-openwhisk-a-snap/