- Posted on
Tue Sep 19, 2017 9:24 am
-
jay (support)
offline
- Site Admin
-
- Posts: 18220
- Joined: Mar 19, 2008
- Location: Austin, Texas
-
Not at the moment. From an implementation standpoint we built the actions (and action groups) to be completely independent of any other objects. In hindsight, it would have been useful to be able to pass through data that would allow an action to know what caused it to be executed. This is definitely something that's on our request list for a future version, but it's a non-trivial task so we have no idea when we might get to it.
There is a workaround (albeit pretty hacky) - create an action per trigger/schedule that updates a variable with an identifier for the trigger/schedule and an action that just executes the common action group (perhaps with a slight delay to make sure the var has time to update). Anything in the action group would then have access to the variable which would identify how it was called. Definitely not perfect (race conditions might make this not work well) but it might work well enough for your purpose.