Commands  ›   ›  Update Clash Result Status

Update Clash Result Status

writes to model Public API · not yet exposed

Coming soon

What you'll see in the chat

on start
Updating clash status in QA XML…
thinking
Reading clashId and newStatus from command parameters…
Persisting the status attribute on the matching clash row…
on success
Clash {clashId} status set to {newStatus}.
on failure
Could not update clash status: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/update_clash_result_status
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

update clash status · change clash status · clash status

Pillar