Based on the available documentation, when you perform bulk operations in Permit.io, the operations return a bulk operation result that includes details about which operations succeeded and which failed (1) (2) (3) . Looking at the Python SDK implementation, bulk operations return specific result objects like

UserCreateBulkOperationResult

,

UserReplaceBulkOperationResult

,

UserDeleteBulkOperationResult

, and

ResourceInstanceCreateBulkOperationResult

(2) (3) . These result objects contain information about the outcome of each individual operation within the bulk request.

async def bulk_create(self, users: List[UserCreate]) -> UserCreateBulkOperationResult:

(3)

async def bulk_replace(self, users: List[UserCreate]) -> UserReplaceBulkOperationResult:

async def bulk_delete(self, users: List[str]) -> UserDeleteBulkOperationResult:

The bulk operations are currently limited to 1000 items per call (1) . However, the documentation doesn't specify the exact structure of the response objects or whether there's an option to make the entire operation fail if a single item fails. For handling failed items and recovery options, I don't have specific information about: • The exact response structure showing which items succeeded vs failed • Whether there's a configuration option for atomic/all-or-nothing bulk operations • Built-in recovery mechanisms for failed items I'd recommend reaching out to Email for more details on bulk operation failure handling and recovery strategies, as this specific behavior isn't detailed in the available documentation.

To learn more, see the sources I considered: [[1] Perform Bulk Operations](https://docs.permit.io/how-to/bulk-operations) [[2] https://github.com/permitio/permit-python/blob/main/permit/api](https://github.com/permitio/permit-python/blob/main/permit/api) [[3] https://github.com/permitio/permit-python/blob/main/permit](https://github.com/permitio/permit-python/blob/main/permit)

@Yilmaz Alizadeh Our bulk APIs are generally atomic, so if one operation fails, the entire request fails. You can check the HTTP status code to know if it succeeded. However, for bulk endpoints, a 409 Conflict is usually ignored—meaning the bulk operation will complete successfully, and the conflicting items will be skipped. Some endpoints, like bulk create role assignments, also have flags (e.g.,

missing_user_policy

) to handle edge cases, but by default there’s no option for partial success.