# Property breaks > Every break of a property that a can-i-deploy report can print, with the fix of each side. This page lists every break of a property that the [report](https://bidirekt.com/docs/ship/can-i-deploy.md#the-report) can print, with the fix of each side. Each one is about a body the provider produces or a body the consumer produces (REST: a response or a request, see [Resources](https://bidirekt.com/docs/rest/resources.md)), and counts only where the property's parent is present ([Which side decides](https://bidirekt.com/docs/contracts/the-contract-file.md#which-side-decides)). `` is the participant under check and `` the counterpart it breaks. ## Absent properties #### ` reads it, but doesn't provide it` Body the provider produces: the participant requires a property the provider does not declare, inside a parent the provider declares. - Fix of ``: `stop reading it, or handle its absence in the code and mark it optional` - Fix of ``: `provide it` #### ` doesn't provide it, but reads it` Body the provider produces: the consumer requires a property the participant does not declare, inside a parent the participant declares. - Fix of ``: `provide it` - Fix of ``: `stop reading it, or handle its absence in the code and mark it optional there` #### ` requires it, but only sometimes provides it` Body the provider produces: the participant requires a property the provider marks optional. - Fix of ``: `handle its absence in the code, then mark it optional` - Fix of ``: `always provide it there` #### ` provides it only sometimes, but requires it` Body the provider produces: the consumer requires a property the participant marks optional. - Fix of ``: `always provide it` - Fix of ``: `handle its absence in the code, then mark it optional there` #### ` doesn't send it, but requires it` Body the consumer produces: the provider requires a property the participant does not send, inside a parent the participant sends. - Fix of ``: `send it` - Fix of ``: `stop requiring it, then mark it optional there` #### ` requires it, but doesn't send it` Body the consumer produces: the participant requires a property the consumer does not send, inside a parent the consumer sends. - Fix of ``: `stop requiring it, then mark it optional` - Fix of ``: `send it` #### ` sends it only sometimes, but requires it` Body the consumer produces: the provider requires a property the participant marks optional. - Fix of ``: `always send it` - Fix of ``: `handle its absence in the code, then mark it optional there` #### ` requires it, but sends it only sometimes` Body the consumer produces: the participant requires a property the consumer marks optional. - Fix of ``: `handle its absence in the code, then mark it optional` - Fix of ``: `always send it there` ## Types #### ` reads it as , but provides ` Body the provider produces: the participant reads the property as a type that does not accept the type the provider declares. - Fix of ``: `read it as ` - Fix of ``: `provide it as there` #### ` provides it as , but reads ` Body the provider produces: the consumer reads the property as a type that does not accept the type the participant declares. - Fix of ``: `provide it as ` - Fix of ``: `read it as there` #### ` sends it as , but expects ` Body the consumer produces: the provider expects the property as a type that does not accept the type the participant sends. - Fix of ``: `send ` - Fix of ``: `accept there` #### ` expects it as , but sends ` Body the consumer produces: the participant expects the property as a type that does not accept the type the consumer sends. - Fix of ``: `accept ` - Fix of ``: `send there` ## Null #### ` doesn't accept null, but may provide null` Body the provider produces: the provider marks the property nullable and the participant does not. - Fix of ``: `handle null in the code, then mark it nullable` - Fix of ``: `stop providing null there` #### ` may provide null, but doesn't accept it` Body the provider produces: the participant marks the property nullable and the consumer does not. - Fix of ``: `stop providing null` - Fix of ``: `handle null in the code, then mark it nullable there` #### ` may send null, but doesn't accept it` Body the consumer produces: the participant marks the property nullable and the provider does not. - Fix of ``: `stop sending null` - Fix of ``: `handle null in the code, then mark it nullable there` #### ` doesn't accept null, but may send it` Body the consumer produces: the consumer marks the property nullable and the participant does not. - Fix of ``: `handle null in the code, then mark it nullable` - Fix of ``: `stop sending null there`