---

name: sentry-unresolved-error-investigation description: "Find unresolved Sentry issues and inspect representative project events."

Sentry Unresolved Error Investigation

Find unresolved Sentry issues and inspect representative project events.

Required Aident Actions

• <action-tag>composio:sentry_tools:sentry_retrieve_project_issues_list</action-tag> (required inputs: organization_id_or_slug, project_id_or_slug): Retrieves a list of issues for a Sentry project, defaulting to unresolved issues unless an empty query string is provided or specific hashes are used.
• <action-tag>composio:sentry_tools:sentry_get_project_events</action-tag> (required inputs: organization_id_or_slug, project_id_or_slug): Retrieves a list of error events for a specified project within a Sentry organization, with options for pagination and detail level.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. IAction · Retrieve Project Issues Listt and quoted cost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply thAction · Get Project Eventsuity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Scope organization, project, environment, and time window before querying.
• Group recurring errors and cite issue and event identifiers for the highest-impact findings.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.