Breakpoint optimized away

I was testing my application and received a nice new warning I had never seen before: Breakpoint could not be set in microflow 'Facturen.Budgethouder_Controle'. Possibly because the action activity was optimized away. How can a breakpoint be optimized away? Now the breakpoint is just ignored and I can not set the best point to break the microflow (in between two iterations).
1 answers

Never seen that warning either, but I think I know what could cause this:

A few combinations of microflow actions are automatically optimized by Mendix into one action when you run the microflow. For example, if you retrieve a list of objects from the database and then only use that list to calculate some aggregation (sum, count, etc), Mendix won't actually retrieve this (potentially huge) list but will execute the aggregation on the database directly. In this case I'm guessing that setting a breakpoint on that retrieve action will cause your warning.

If this indeed is what's causing this, try setting the breakpoint on another (earlier) action.