Schema rollback scope in Insomnia Designer after OpenAPI changes

Question

Insomnia Designer provides a schema validation mode for OpenAPI and GraphQL documents and a documented undo schema change action that restores a temporary workspace snapshot without losing other workspace data. The rollback relies on internal version history stored in the workspace file and is described for Designer 2023.5.0 and later.

The documented limits include session-bound undo history that is cleared on restart, a requirement that the workspace be saved to disk for rollback to be available, and no automatic change to environment variables or request collections that reference the schema.

An unresolved behavior concerns consistency of dependent artifacts. Does rolling back a schema change also revert test scripts or generated client code that were updated based on the new schema, or do those artifacts remain modified and become out of sync with the reverted schema? What is the supported scope of the rollback with respect to workspace artifacts beyond the schema node?

Tasadduq Burney · Answer

Rolling back a schema change only restores the definition node; test scripts, request bodies and generated client code remain unchanged and can become out of sync with the reverted schema.

Confirmed facts

Undo history is session‑bound and is cleared when the application restarts.
The workspace must be saved to disk for the snapshot to be available.
Only the schema definition node is reverted; other workspace artifacts are untouched.
Environment variables referencing schema properties stay unchanged after rollback.
Generated client code is external to the workspace undo history.

Likely explanation

Insomnia treats the schema as a validation source and treats requests, tests and environment variables as separate entities. Because the undo action targets the schema node only, dependent artifacts are not automatically synchronized.

Steps to verify scope

Modify a property in the OpenAPI schema.
Update a request body to use the new property.
Trigger Undo Schema Change.
Observe that the schema returns to the old property while the request body retains the new property.

Missing diagnostic detail

Is the workspace stored as a local file or a synchronized cloud workspace? This determines whether session‑bound undo history can be reliably retained across restarts.

Schema rollback scope in Insomnia Designer after OpenAPI changes

1 answer

Confirmed facts

Likely explanation

Steps to verify scope

Missing diagnostic detail

Your perspective belongs here.

0 question comments