<!--
{
  "availability" : [
    "macCatalyst: 13.0.0 -",
    "macOS: 10.0.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "Foundation",
  "identifier" : "/documentation/Foundation/DistributedNotificationCenter/SuspensionBehavior/deliverImmediately",
  "metadataVersion" : "0.1.0",
  "role" : "Case",
  "symbol" : {
    "kind" : "Case",
    "modules" : [
      "Foundation"
    ],
    "preciseIdentifier" : "c:@E@NSNotificationSuspensionBehavior@NSNotificationSuspensionBehaviorDeliverImmediately"
  },
  "title" : "DistributedNotificationCenter.SuspensionBehavior.deliverImmediately"
}
-->

# DistributedNotificationCenter.SuspensionBehavior.deliverImmediately

```
case deliverImmediately
```

## Discussion

The server delivers notifications matching this registration irrespective of whether [`suspended`](/documentation/Foundation/DistributedNotificationCenter/suspended) with an argument of <doc://com.apple.documentation/documentation/Swift/true> has been called. When a notification with this suspension behavior is matched, it has the effect of first flushing any queued notifications. The effect is as if [`suspended`](/documentation/Foundation/DistributedNotificationCenter/suspended) with an argument of <doc://com.apple.documentation/documentation/Swift/false> were first called if the application is suspended, followed by the notification in question being delivered, followed by a transition back to the previous suspended or unsuspended state.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)