instance-management

Safely switch between ServiceNow instances by using explicit per-environment targeting and context verification before performing any operation. This ensures the target environment is selected and prevents cross-environment edits.

Preventing accidental production edits requires per-environment isolation and current-instance checks. You must explicitly target your instance and verify the context before executing operations to ensure actions stay isolated.

Context verification for multi-instance workflows works by enforcing a current-instance check before any operation. It requires explicit instance targeting to validate that the selected environment matches the intended target before proceeding.

Yes, you can manage multiple ServiceNow instances using MCP tools, REST endpoints, and native commands. The skill satisfies multi-instance configuration and per-operation targeting across development, test, and production contexts.

Yes, explicit instance targeting is required for every operation across environments. Per-operation targeting and context verification ensure the correct ServiceNow environment is selected before any action is performed.

Environment switching fails without context verification because there is no validation of the current instance before operations. Explicit per-environment targeting and context checks are required to ensure isolated deployments and prevent errors.