---
title: "Force Unlock Sync Configuration"
method: POST
path: "/v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock"
tags: ["Bucket Syncs"]
---

# Force Unlock Sync Configuration

`POST /v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock`

Force-release a distributed lock on a sync configuration.

Use this when a sync trigger returns 'skipped_already_running' but no sync
is actually executing (zombie lock from a crashed worker).

## Path parameters

- `bucket_id` string, required
- `sync_config_id` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `422` — Validation Error
- `500` — Internal Server Error

---

[API](https://skmtc.net/mixpeek/apis/mixpeek-api.md) · [All operations](https://skmtc.net/mixpeek/apis/mixpeek-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mixpeek/mixpeek-api/revisions/1c7f31821424/schema)