I've just come across this issue myself, what I found worked was deleting the global policy on there, then remaking it using the same names and specifications, then using the "service-policy [global_policy] global" command to make that policy the glo...