ASM policy synchronising as 'not configured'

I've de-sync'd them and even uninstalled/reinstalled ASM on both devices and I'm still getting the same issue. I should note that at the moment there is no traffic on the VIP associated with the single ASM policy and the policy has Application language set to auto detect so is it possible that the policy on the second device is in this state because the application language has not yet been discovered? I have just created a policy with the Application language set and this appears to resolve the issue. Once we have traffic across the virtual servers I'll update this stream on whether the policies have automatically completed their configuration.