More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Cloud Run Revision Traffic Cookie Pin

    1

    Resolve Cloud Run sessions pinned to drained revisions after traffic shifts

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Cloud Run Revision Traffic Cookie Pin

    Repair Cloud Run Revision Traffic Cookie Pin

    Example session with this skill installed

    Clients keep reaching an old revision despite a completed rollout.

    Available evidence: revision traffic table (partial). Additional evidence requested: state and configuration snapshot, error and recovery logs, deployment and alert timeline. Review the case, identify open evidence gaps, and do not invent a live test or production change.

    • Read your context and instructions
    • Compiled the repair cloud run

    Repair Cloud Run Revision Traffic Cookie Pin — EVIDENCE-LIMITED REVIEW

    Scenario received

    Clients keep reaching an old revision despite a completed rollout.

    Source register

    • S1: revision traffic table — PARTIAL SOURCE PROVIDED.
    • S2: state and configuration snapshot — NOT PROVIDED; REQUIRED TO VERIFY.
    • S3: error and recovery logs — NOT PROVIDED; REQUIRED TO VERIFY.
    • S4: deployment and alert timeline — NOT PROVIDED; REQUIRED TO VERIFY.

    Concrete checks

    1. compare traffic splits and session-affinity cookies — PRELIMINARY, NOT VERIFIED.
    2. validate rollback and cookie expiry policy — AWAITING CORROBORATING EVIDENCE.
    3. crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
    4. record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.

    Deliverables / acceptance gates

    • revision traffic table evidence map: DRAFT / INCOMPLETE until evidence is validated.
    • old revision exception register: DRAFT / INCOMPLETE until evidence is validated.
    • valid routing validation plan: DRAFT / INCOMPLETE until evidence is validated.

    Decision

    INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stale session affinity in Google Cloud Run can trap users on deprecated revisions even after a 100% traffic shift. This skill provides an evidence-based diagnostic framework to identify why clients are pinned to old revisions and generates a plan to restore correct routing.

    What it does

    • Traffic comparison maps current traffic splits against active session-affinity cookies to find mismatches.
    • Policy validation audits rollback settings and cookie expiry configurations for misalignments.
    • Evidence mapping creates a structured register of old revision exceptions based on logs and timestamps.
    • Verification gating generates a routing validation plan with reversible steps to clear stale pins.

    How it works

    1. Supply the revision traffic table, configuration snapshots, and deployment timelines.
    2. The skill executes an evidence-led procedure to crosscheck timestamps and version identifiers.
    3. It classifies every finding as VERIFIED, CONTRADICTED, UNVERIFIED, or NOT APPLICABLE.
    4. You receive a structured output artifact detailing the routing exceptions and a recovery plan.

    Frameworks & tools

    This tool targets Google Cloud Run environments, specifically those utilizing session affinity and revision-based traffic management.

    Why this beats prompting it yourself

    Standard prompts often guess at cloud configuration errors. This skill enforces strict decision discipline, requiring specific source IDs and timestamps to prevent hallucinated diagnostic conclusions.

    Use cases

    • Debugging why a subset of users still sees an old UI after a successful production rollout.
    • Auditing session affinity policies during high-stakes blue-green deployments.
    • Investigating persistent 404 or 503 errors caused by requests hitting drained revisions.

    Known limitations

    Does not have direct cloud access. Requires manual input of log snippets, traffic tables, and configuration snapshots to function.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    Permissions

    Read Files

    Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.

    Listed20 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill identifies why users remain 'stuck' on old revisions despite a 100% traffic shift, providing a structured recovery plan to clear stale session-affinity cookies and restore correct routing.

    The skill is compatible with any LLM that supports structured data input, including GPT-4, Claude 3, and Gemini, provided you can input text-based logs and configuration snapshots.

    You will receive the complete diagnostic workflow, the evidence-mapping framework, and a template for generating reversible verification gating plans.

    No, the skill operates on manual inputs like traffic tables and log snippets to maintain security; it does not require or request direct API access to your Google Cloud environment.

    Yes, it is designed for any deployment strategy utilizing Cloud Run session affinity, including complex blue-green rollouts and canary releases where revision pinning is active.

    By enforcing a 'Verification Gating' discipline, the skill requires specific timestamps and source IDs for every claim, preventing the AI from guessing or hallucinating non-existent configuration errors.

    New in DevOps & Cloud