メニュー
Diagnose and recover a troubled/wedged Interoperability production, following the recover-first, clean-last-resort escalation ladder. Never suggests killAppData without the user's explicit acceptance of persistent business-state loss.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review and promote configuration/code drift from a source IRIS environment to a target using the review-before-write iris_env_diff -> iris_env_promote workflow (scoped diff, plan, an explicit user-selected step allowlist, confirmed execute, re-diff verify). Never acts on onlyInTarget warnings -- never deletes a target-only item, in any action.
Resend failed Interoperability messages for a config item using the dry-run-first iris_message_resend workflow — preview the match count before executing, then verify the new headers via iris_production_messages. States the duplication hazard and that resend/resendFiltered are governance-default-disabled writes.
Audit the IRIS instance's security posture: users (default passwords, %All holders), roles, service authentication settings, SSL/TLS configs, and instance auditing status.
Run a full IRIS instance health check (iris_health_check) and interpret every non-ok finding, naming the fixing tool for each one.
Deploy an ObjectScript class or package to IRIS (iris_doc_load, glob-path form), fix compile errors, then run its unit tests (iris_execute_tests) with a total-count check.
Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.
| name | recover-stuck-production |
| description | Diagnose and recover a troubled/wedged Interoperability production, following the recover-first, clean-last-resort escalation ladder. Never suggests killAppData without the user's explicit acceptance of persistent business-state loss. |
No production class name given — discover it from iris_production_status (its name field) in step 1.
No namespace specified — omit namespace to use the server's configured default on every call below.
Escalation ladder — follow IN ORDER, do not skip ahead:
iris_production_status (with detail: true) to see the current production name and state (Running/Stopped/Suspended/Troubled/NetworkStopped).iris_production_summary (cross-namespace, no namespace param) and iris_production_queues to locate stuck or backed-up items — queues that are not draining, items reporting errors.iris_production_logs filtered by itemName and/or type: "Error" to understand what is actually wrong.iris_production_control action 'recover' FIRST (pass name: "<production>" if known). This attempts to restart a troubled production without touching stored state.iris_production_status) — if the production is now healthy, STOP here; report success.iris_production_control action 'clean' — this clears STALE TRANSIENT runtime state (queues, job-status, suspended messages) that 'recover' cannot fix. This is a last resort, not a first response.killAppData: true on the 'clean' action unless the user has EXPLICITLY and knowingly accepted that it wipes PERSISTENT Ens.AppData business state (HL7 sequence numbers, file/FTP done-file tables — wiping these causes re-ingestion and DUPLICATE messages — and RecordMap/X12 batch/control-number state). If considering it, first explain the consequence to the user IN FULL and require an explicit "yes, I accept the data loss" before passing killAppData: true AND confirm: true together (both are required; this is a deliberate double confirmation gate).iris_production_status to verify a healthy restart before reporting success.