OCI Function Troubleshoot

Use this skill to isolate the most likely cause of an OCI Functions problem from error text, command output, or observability signals.

This skill is diagnosis-first and non-mutating by default:

• prefer read-only checks
• do not edit Fn context, log into Docker, create or update apps, redeploy, or change infrastructure unless the user explicitly asks to execute a fix
• if the user wants the fix executed, finish the diagnosis first and hand off mutating remediation to $oci-functions-deploy

Output Contract

Always answer in this exact shape:

• stage: one of setup_or_control_plane, create, deploy, invoke, observability_first
• evidence: 1-3 concrete facts from the user's error text, command, config, logs, metrics, or limits
• most_likely_cause: one primary cause, or a ranked top-2 shortlist when confidence is low
• confidence: low, medium, or high
• next_confirming_check: the single best read-only check to narrow or confirm the cause
• smallest_safe_remediation: the least invasive next action; if evidence is weak, this can be "collect more evidence with ..."
• validation: the follow-up step that proves the remediation worked

Triage