Skip to content
Plune Plune Docs

Rebuild the Steps Database of every project from its live manual cases

POST
/v1/admin/reindex-steps
 
curl --request POST \
  --url https://beta-api.plune.ai/v1/admin/reindex-steps \
  --header 'Authorization: Bearer <token>'

The migration creates the Steps Database empty while the manual cases already carry their steps. This re-syncs every live manual case of every project through the same writer the case save path uses (D10) — once after the deploy that brings the table, like reindex-tags after its own. Steps made by hand that no case carries are left alone. reindexed counts the cases walked. Owner-only, like file-unfiled; everyone else gets 404.

Authorizations

Section titled “Authorizations ”

Responses

Section titled “ Responses ”

200

Section titled “200 ”

How many cases were walked, per project

Media type application/json
object
projects
required
Array<object>
object
projectId
required
string
reindexed
required

Live manual cases re-synced into the Steps Database in this run.

integer
Example 
{
  "projects": [
    {
      "projectId": "userA::default",
      "reindexed": 212
    },
    {
      "projectId": "userB::default",
      "reindexed": 0
    }
  ]
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

The caller does not own the application

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

429

Section titled “429 ”

Rate-limited: either the per-route throttle or a tenant quota. Retry-After carries the seconds until the window rolls over.

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

Headers

Section titled “Headers ”
Retry-After
integer

Seconds until the window rolls over