funasr-task-manager-emergency-stop

Stop FunASR tasks, release server slots, and clean scheduler state.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wangminle/funasr-task-manager --skill funasr-task-manager-emergency-stop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: funasr-task-manager-emergency-stop
Source: https://github.com/wangminle/funasr-task-manager/tree/main/6-skills/funasr-task-manager-emergency-stop
Command: npx skills add https://github.com/wangminle/funasr-task-manager --skill funasr-task-manager-emergency-stop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires admin-api, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses emergency scenarios in the FunASR Task Manager, such as immediate task cessation, server slot release, and recovery from scheduler pollution.

Core Features & Use Cases

  • Emergency Task Cessation: Quickly stop running transcription tasks and release occupied server slots.
  • Segment Management: Clear zombie segments and diagnose active slot usage.
  • Scheduler Recovery: Recover from scheduler pollution after canceled batches.
  • Use Case: When a user needs to immediately stop all tasks due to an unexpected situation, this Skill can be used to ensure that resources are properly released and the system can be quickly brought back to a stable state.

Quick Start

To initiate an emergency stop, run the following command: python -m cli admin emergency-stop --scope all --confirm

Frequently Asked Questions about funasr-task-manager-emergency-stop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform an emergency stop for FunASR tasks and release server slots?

Emergency task cessation in FunASR quickly stops running transcription tasks and releases occupied server slots, bringing the system back to a stable state during unexpected situations.

How do I recover the FunASR scheduler from pollution after canceled batches?

Yes, the emergency stop process includes scheduler recovery to clear zombie segments and diagnose active slot usage, effectively cleaning up the system after canceled batches and preventing resource leaks.

Do I need admin API access to execute an emergency shutdown on the FunASR Task Manager?

Yes, admin API access is required to execute an emergency shutdown on the FunASR Task Manager, ensuring authorized personnel perform immediate task cessation, server slot release, and scheduler cleanup.

What precautions should I take before running an emergency stop on FunASR transcription tasks?

Before running an emergency stop on FunASR transcription tasks, carefully confirm the shutdown scope to prevent data loss, as immediate task cessation will halt all active processing and clear zombie segments.

Why does the FunASR emergency stop command require explicit user confirmation?

The FunASR emergency stop command requires explicit user confirmation to prevent accidental data loss, ensuring administrators intentionally authorize immediate task cessation and resource recovery before execution.