Thanks for flagging this! I’ve been able to reproduce the first case (shared component), so that one looks like a genuine issue — I’ve logged an internal challenge for it and we’ll take a closer look from there.
For the second case with the action, I haven’t been able to reproduce it on my end. Could you share a bit more detail on how that action is set up? And does it happen for all similar actions, or only this specific one?
That’s good. Will you let me know when the bug is fixed?
Not sure what more to say. My setup is two very generic actions. One for logging and one to log errors. When calling the *Log action from my *Error action I get the error message in App Health. My Log action takes 3 params, none of them are required and all of them are populated in the Run Action node.
To me it seems like the same issue as with shared components.