---
title: "Conflict (Calendar)"
description: "A conflict between two events caused by overlapping event resource requests."
---

> Documentation Index
> Fetch the complete documentation index at: https://planningcenterkit.mackenly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Conflict (Calendar)

A conflict between two events caused by overlapping event resource
requests.

If the conflict has been resolved, `resolved_at` will be present.

| Property | Value |
| --- | --- |
| Product | [Calendar](/reference/calendar/) (`pco.calendar`, API version `2026-06-22`) |
| Resource type | `Conflict` |
| TypeScript | `Calendar.Conflict`, attributes `Calendar.ConflictAttributes`, schema `Calendar.ConflictSchema` |
| Planning Center path | `/calendar/v2/conflicts` |
| Planning Center docs | [Conflict](https://api.planningcenteronline.com/docs/apps/calendar/versions/2026-06-22/vertices/conflict) |

## How to reach it

| Client path | Returns | Filters | Create |
| --- | --- | --- | --- |
| `pco.calendar.conflicts` | Collection | `future`, `resolved`, `unresolved` | No |
| `pco.calendar.events.id(eventId).conflicts` | Collection |  | No |
| `pco.calendar.resources.id(resourceId).conflicts` | Collection |  | No |

From a collection, `.id(conflictId)` addresses one Conflict: `pco.calendar.conflicts.id(conflictId)`. Collections support [`where`, `include`, `order`, and pagination](/guides/querying/); single resources have `get()`.

## Attributes

On `Calendar.ConflictAttributes`. Every resource also has `id` and `type` (`'Conflict'`) next to its attributes.

| Name | Type | Description |
| --- | --- | --- |
| `created_at` | `string \| null` | UTC time at which the conflict was created |
| `note` | `string \| null` | Additional information about the conflict or resolution |
| `resolved_at` | `string \| null` | UTC time at which the conflict was resolved |
| `updated_at` | `string \| null` | UTC time at which the conflict was updated |

## Relationships and includes

Side-load with `include()` (or `get({ include })`) and read with `related(resource, name)`: `resolved_by`, `resource`, `winner`.

| Relationship | Type | To | Includable |
| --- | --- | --- | --- |
| `resolved_by` | To one | [Person](/reference/calendar/person/) | Yes |
| `resource` | To one | [Resource](/reference/calendar/resource/) | Yes |
| `winner` | To one | [Event](/reference/calendar/event/) | Yes |

## Querying

No documented `where` fields.

### Order

`order(...)` accepts these fields, ascending, or descending with a `-` prefix: `resolved_at`.

### Filters

`filter(...)` names depend on the edge you query through:

| Edge | Filters |
| --- | --- |
| `pco.calendar.conflicts` | `future`, `resolved`, `unresolved` |

## Edges

Follow these from one Conflict, `ref = pco.calendar.conflicts.id(conflictId)`:

| Edge | Leads to | Returns | Filters | Create |
| --- | --- | --- | --- | --- |
| `ref.resolved_by` | [Person](/reference/calendar/person/) | Collection |  | No |
| `ref.resource` | [Resource](/reference/calendar/resource/) | Collection |  | No |
| `ref.winner` | [Event](/reference/calendar/event/) | Collection |  | No |

## Writing

| Property | Value |
| --- | --- |
| Create | No |
| Update | No |
| Delete | No |

## Example

```ts
import type { Calendar } from '@mackenly/planningcenterkit';

const page = await pco.calendar.conflicts.order('resolved_at').perPage(25).list();
const items: Calendar.Conflict[] = page.data;
```

Source: https://planningcenterkit.mackenly.com/reference/calendar/conflict/index.mdx
