When flagging content from a rule, the flagged content is cached

I have a set of rules that looks like this:

1. (rule) When flag A is set, do this:
   1. (action) set field X on flagged content
   2. (action) save flagged content
   3. (action) set flag B on flagged content
2. (rule) When flag B is set, do this:
   1. Create new node
   2. (action) copy field X on flagged content to field Y in the new node

The problem is that the second rule does not see the new value of field X set in the first rule. It seems that this is caused by the fetch_content() method in flag_flag which caches the node too eagerly. Adding a "load content" action to the second rule which loads a node based on the flagged content's node ID (effectively reloading it) helps.

This is a problem because it introduces tight coupling between these rules (reloading the node in the first rule and flagging the reloaded node there didn't help!); the second rule needs to know it might be triggered as a result of executing the first rule (it can also be executed manually in the site I'm using this in).