Bucket Syncs

Force Unlock Sync Configuration

Changed on

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).

post/v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock

Request

  • Base URL: https://api.mixpeek.com
  • URL: https://api.mixpeek.com/v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock
  • Auth: HTTP bearer and API key in header X-Namespace

Path parameters

bucket_idstring required
sync_config_idstring required

Response

Successful Response

unknown required

Changes

  • 61a175e8eb9aRevision changes
    • warning

      removed the optional property from the response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status

  • 5d4c905106b4Revision changes
    • info

      the endpoint scheme security BearerAuth AND NamespaceHeader was added to the API