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

# v2.73.0 - Schedule Backfill Improvements

> The resource field is now optional on the schedule backfill endpoint, and a new dry_run flag lets you preview which connections would be affected before committing changes

**Released 18th September 2026**

<Check>
  **Backward-compatible release:** All changes are additive or relax existing constraints. No existing integrations are affected.
</Check>

## Schedule backfill enhancements

`POST /v2/integrations/connections/schedules/backfill` has two new capabilities in this release.

### `resource` is now optional

Previously, `resource` was a required field and you had to name a specific resource type (such as `VEHICLE` or `HOS`) to run a backfill. It is now optional.

When you omit `resource`, the endpoint syncs every active connection against the full adapter registry: each connection gains whatever schedules its TSP has implemented adapters for and is currently missing. This makes it straightforward to bring all connections up to date after a new adapter is deployed, without needing to know which resource types were added.

```bash theme={null}
# Backfill all missing schedules across all connections
POST /v2/integrations/connections/schedules/backfill
Content-Type: application/json

{}
```

```bash theme={null}
# Backfill a specific resource type (unchanged behaviour)
POST /v2/integrations/connections/schedules/backfill
Content-Type: application/json

{
  "resource": "VEHICLE"
}
```

### New `dry_run` flag

A new optional boolean field `dry_run` lets you preview which connections would receive new schedules without actually creating any rows. The response returns the same `connection_ids` list as a live run, but no schedules are written to the database.

```bash theme={null}
POST /v2/integrations/connections/schedules/backfill
Content-Type: application/json

{
  "dry_run": true
}
```

```json theme={null}
{
  "connection_ids": ["conn_abc123", "conn_def456"]
}
```

Set `dry_run` to `false` or omit it entirely to perform the backfill for real.

### Summary of request body changes

| Field | Before | After |
| - | - | - |
| `resource` | Required string | Optional — omit to target all resource types |
| `dry_run` | Not available | Optional boolean (default `false`) |

***

## Need help?

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/integrations-api">
    View complete endpoint documentation for the Integrations API
  </Card>

  <Card title="Contact support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about this release? Our team is here to help
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.