Cisco FMC access control policy POST a 'BLOCK' action using API

[Marius Gunnerud]

I am trying to post a rule using {'action': 'BLOCK'} but this is failing.  If I change the action to {'action': 'ALLOW'} the POST is successful.  I have configured a rule with the block action in GUI and then checked the output in api-explorer and there the action is also shown as 'BLOCK' so I am uncertain why this is happening.  Anyone seen this issue before and / or have any suggestions on how to remedy the issue?

This is quite odd.  All block posts fail (i.e. BLOCK, BLOCK_REST, etc.) but ALLOW, TRUST, and MONITOR work fine.  Could this be a bug in the 6.7?

This is the configuration that is being POSTed:

{'action': 'BLOCK',
'destinationNetworks': {'objects': None},
'destinationPorts': {'objects': None},
'destinationZones': {'objects': None},
'enabled': False,
'logEnd': True,
'name': 'Deny Any',
'sendEventsToFMC': True,
'sourceNetworks': {'objects': None},
'sourceZones': {'objects': [{'id': 'd5997ca8-54bb-11eb-920e-f851204a1f7d',
'name': 'LAN_Zone',
'type': 'SecurityZone'}]},
'type': 'AccessRule'}
Error in connection --> 400 Client Error: 400 for url: https://192.168.0.50/api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/policy/accesspolicies/000C29C8-1550-0ed3-0000-017179869187/accessrules