illustrator_connection_status
Diagnose Illustrator connection issues by identifying the first broken link among WebSocket, panel, Illustrator, or document. Receive recovery steps or run a probe for deeper checks.
Instructions
Report whether Illustrator is reachable, and what to fix if not.
CONTRACT: readOnly=True, destructive=False, idempotent=True, openWorld=False
WHEN TO USE:
A call failed with a connection error and you need to know which link broke
Before a session, to confirm the panel is connected
To check whether the panel is busy rather than gone
KEY CONCEPTS: Four layers, outermost first: this server's WebSocket listener, the CEP panel's socket, Illustrator itself, and the active document. The first one that is not ok is reported as blockedAt, and the recovery steps address that link only. Layers behind a broken one read 'unknown' rather than being guessed at.
OPTIONS: probe=false (default) — instant, reads process-local state only probe=true — also round-trips a tiny read-only script to Illustrator
EXAMPLES: Instant report, no host call: {"params": {}} Also confirm Illustrator itself answers: {"params": {"probe": true}}
RESULT: data.ready is true only when every layer is up. data.blockedAt names the first broken layer, or is null. data.recovery lists the steps for it. execution reports whether this report was produced, never whether the connection is healthy — a successful report of a dead panel is a success.
NOTES:
Never starts the server and never reconnects
Trusted probe timeouts retire local waits and require a readiness fence; blocking names the retained job and exact job_status call
Answers normally when Illustrator is closed, which is the point
Without probe, the document name is last-known, not live
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |