Skip to content
Get packs

Application Integration Troubleshooting

Diagnose failed, stuck, or silent Google Cloud Application Integration runs and connector tasks.

Source Download skill
Repository
google/skills
Stars
21,782
Licence
Apache-2.0
Files
7 files

What it does

When an Application Integration workflow on Google Cloud fails, hangs in a suspended or retry state, or returns success without doing its work, this skill guides the agent through a fixed checklist. It checks whether an execution actually ran and what state each task reached, inspects logs and monitoring, probes Integration Connectors health, and checks IAM, service account, and quota problems. Read-only checks run freely, while changes such as canceling runs, lifting suspensions, or installing packages require the user's explicit approval.

Great for

  • Developers whose Google Cloud Application Integration flows fail or stall in production or staging
  • Engineers debugging Integration Connectors tasks that return errors or unhealthy status
  • Teams that need a repeatable, read-first investigation process before changing live integrations

Skip it if

  • Initial region setup, API enablement, or product onboarding, which belong to the sibling application-integration-basics skill
  • Building, editing, or publishing integrations, which belong to application-integration-authoring; this skill does not cover that work
  • Non-Google-Cloud workflow tools, since the skill is specific to Application Integration and its REST API

Try asking

  • “My Application Integration run returned HTTP 200 but nothing was written to the database. Help me find out why.”
  • “This integration has been suspended for hours in europe-west1. Walk me through checking the suspension and its state.”
  • “My Integration Connectors task keeps failing with a permission error. Check IAM and the run-as service account.”
  • “Check the logs and execution records for integration X in us-central1 and tell me which task failed.”
Step-by-step guide: how to use Application Integration TroubleshootingInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 7 original files, the Apache-2.0 licence and an attribution note.

    application-integration-troubleshooting.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip application-integration-troubleshooting.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip application-integration-troubleshooting.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent the integration name, execution ID, and region up front so it can start with executions.list instead of guessing.
  • Keep the agent in read-only mode until you have reviewed each command it proposes; approve state-changing steps such as cancel, replay, or suspension lifts one at a time.
  • Do not treat an HTTP 200 from :execute as success; ask the agent to check the execution record and each task state.

What's inside

  • references/attribution.md
  • references/common-errors.md
  • references/connectors-health.md
  • references/execution-states.md
  • references/logging-and-monitoring.md
  • references/suspensions.md
  • SKILL.md

Redistributed unmodified from google/skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.