In general yes but I think generally do you need the transaction id or the
parent id for an activation?

This issue is relevant -
I also recall in the early days of the composer, we wanted a way to query
parent/child activations but this requires new couch views and we didn't
pursue it.

On Thu, Aug 15, 2019 at 1:20 PM Chetan Mehrotra <>

> 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]
> [2]

Reply via email to