The ARA Jenkins plugin *seemingly* creates a package and *then* optionally assigns properties and dynamic properties afterwards. The implication of this if I'm right is that a workflow started from an 'OnEnter' action on the initial package state will have a race with the plugin when it comes to accessing those properties.
To support that I idea I have a setup with a package with a number of properties and a workflow starting in 'OnEnter' which tries to read those properties. When trying this several times I see different number of properties having received their values from the plugin.
So does anyone have some insights on my hunch and secondly how can I make sure my properties are set by the plugin before I access them from my workflow?