Dismiss running or pending jobs and update status to dismissed in Weaver API environments.
npx skills add https://github.com/crim-ca/weaver --skill job-dismiss
Please help me install this Agent Skill. Skill: job-dismiss Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/job-dismiss Command: npx skills add https://github.com/crim-ca/weaver --skill job-dismiss
The job-dismiss skill solves the issue of stopping jobs that are taking too long, have incorrect parameters, or are no longer needed. It provides a straightforward way to cancel and update job statuses to 'dismissed'.
Dismiss a job with ID 'a1b2c3d4-e5f6-7890-abcd-ef1234567890'.
High-intent search queries and answers about installing and using this skill.
To cancel a running job in a Weaver API environment, you can dismiss the job using its specific job ID. This action updates the job status to 'dismissed', halting further execution and immediately freeing up allocated system resources.
You should dismiss a pending job when it has incorrect parameters or is no longer required for your workflow. Dismissing the job prevents unnecessary execution and deallocates the queued resources, ensuring they are available for other tasks.
The best way to handle job cancellation and resource deallocation for pending tasks is to use a job dismissal interface. This approach updates the job status to 'dismissed' and automatically manages the resource cleanup for stopped jobs.
Yes, you need API access with job management permissions to dismiss and update job statuses. This authorization is required to terminate running or pending jobs and handle the associated resource deallocation within the Weaver API environment.
Yes, you can use job dismissal to handle incorrect parameters in a running job. By canceling the job execution, you stop the process from continuing with invalid data, update the status to 'dismissed', and free up the allocated resources.
Dismissing a job updates its status to 'dismissed' to explicitly indicate that the job was manually stopped and its resources were deallocated. This status distinction helps track job termination for long-running or unnecessary tasks within the Weaver API.
crim-caManage and report on Weaver jobs with filtering and pagination.
crim-caExtracts job execution logs with I/O streams and timestamps from Weaver API-driven systems.
kausthubh-coderSchedule and execute recurring background tasks in Convex applications using cron expressions.
labringSet Redis-based stop flags to pause per-app per-chat workflows.
