golem-cancel-queued-invocation

Cancel queued Golem agent invocations by idempotency key before processing starts.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-cancel-queued-invocation-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-cancel-queued-invocation
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-cancel-queued-invocation
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-cancel-queued-invocation-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you cancel an agent invocation that is already enqueued but has not started processing, preventing unnecessary work and avoiding wasted compute time.

Core Features & Use Cases

  • Cancel by idempotency key: Targets the specific pending invocation using its idempotency key, which is the reliable reference when multiple invocations may be in-flight.
  • Works with both golem and golem-cli: Use the same operational intent regardless of which binary you run.
  • Safety for started invocations: Cancellation succeeds only while the invocation is still queued; once processing begins, cancellation fails to avoid inconsistent state.

Quick Start

Run golem agent cancel-invocation <AGENT_ID> <IDEMPOTENCY_KEY> to cancel the pending invocation for that agent using its idempotency key.

Frequently Asked Questions about golem-cancel-queued-invocation

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

FAQPage Schema
How do I cancel a queued agent invocation in Golem?

To cancel a queued agent invocation in Golem, run golem agent cancel-invocation <AGENT_ID> <IDEMPOTENCY_KEY> to remove the pending task before it starts processing.

What happens if I try to cancel a Golem agent invocation that already started?

Canceling a Golem agent invocation fails once processing begins to avoid inconsistent state, ensuring cancellation only succeeds while the invocation is still queued.

Can I cancel a queued invocation using the agent ID instead of the idempotency key?

No, canceling a queued Golem agent invocation requires the specific idempotency key, which reliably targets the pending task when multiple invocations may be in-flight.

Does canceling queued agent work work with both golem and golem-cli?

Yes, canceling queued agent invocations works with both golem and golem-cli binaries, providing the same operational intent regardless of which CLI tool you run.

Why cancel a queued agent invocation instead of letting it process?

Canceling a queued agent invocation prevents unnecessary work and avoids wasted compute time when an enqueued task is no longer needed before execution begins.

When do I need an idempotency key to manage queued agent tasks?

An idempotency key is needed to reliably reference and cancel specific pending Golem agent invocations when multiple tasks are serialized and waiting in the queue.