I've noticed this before and just ran across it again. I'd like
to get this behavior confirmed: when you add an action to a
predicate and then go trigger that predicate, the action doesn't
seem to get performed unless you first clicked the "Save
changes" button on the attributes form. This shouldn't be
necessary given the way the form is supposed to work. This may
also in fact be true for conditions.   That'd be a "confirmed",
there, bud. The "Remove Action" button works without clicking
"Save changes", though.  I think I found why. The action is
present in the database row for the predicate, but it doesn't
look like it's in the right format. There is an #arguments key,
where there should be an #argument_map. There is also not a
#settings key until "Save changes" is clicked. This sounds to me
like there's a bug in the submit handler for "Add action".  Just
ran into that bug...is there a proposed solution for this?  As
Island Usurper noticed, the #argument_map is not inserted into
the serialized actions. The p