---
title: "Clear a section stuck mid-apply"
method: POST
path: "/api/admin/onboarding-questionnaires/{questionnaire_id}/sections/{section_key}/reset"
tags: ["Onboarding Questionnaire - Admin"]
---

# Clear a section stuck mid-apply

`POST /api/admin/onboarding-questionnaires/{questionnaire_id}/sections/{section_key}/reset`

Release an `applying` claim that no longer has a request behind it.

A worker killed mid-apply (a deploy, a pool failure) leaves the section
claimed forever: it can never be applied again AND the whole questionnaire
can never be reopened, because `reopen` refuses while anything is applying.
This is the only way out, and it is why the appliers dedupe per item -- the
retry after a reset has to be harmless.

## Path parameters

- `questionnaire_id` integer, required
- `section_key` string, required

## Headers

- `x-api-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-09-02** `8492136eefc5` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/multigest/apis/multigest-protected-api/changes/api/admin/onboarding-questionnaires/:questionnaire_id/sections/:section_key/reset/post.md)

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/8492136eefc5/schema)