I'm seeing the same thing happen with our foreground notifications that also set content-available, e.g.: { 		"aps" : { "alert" : "Display this message", 				"content-available" : 1 		} } Based on @honishi's reply I'm assuming iOS 14 is treating this as a background update, setting the priority to 5 and throttling delivery. In my specific case, if I send 10 or so push notifications in ~15 seconds the first ~3 will call application:didReceiveRemoteNotification:fetchCompletionHandler: and then the system will stop calling that method for any push notification for some period of time. For background or foreground pushes. (Although all of my pushes have content-available: 1.) As a workaround, at least for foreground notifications, in our UNUserNotificationCenterDelegate I implemented userNotificationCenter:willPresentNotification:withCompletionHandler: which gets called for every push when the app is in the foreground and handled the payload in there. I'm assuming this is a valid solution and not a hack since the docs say: If you implement this method, you can take whatever actions are necessary to process the notification and update your app.