Why can't the CLI push an asset, generate, or export an OPZ?

The ol CLI talks to Hub with ol login (or --api-key) and ol config hub --hub-url. A 401 on ol login --api-key means the key is wrong, expired, or issued on a different Hub (SaaS vs Enterprise).

Push / unknown type

The file extension or parser does not match the module connector (for example a JSON artifact on a screens/RPC module). Use a type that connector lists.

OPZ generate / compatibility version

A warning that the OPZ compatibility version may not match core means the OPZ was produced with a different Hub/core version than the runtime. Re-export from the same Hub version you run, or generate with a matching CLI.

Missing connection details on ol generate --provider opz

The project or module has no resolvable connection id in that environment. Push the module with connections, or pass the connection Hub expects.

Keep CLI version aligned with that Hub. Hub versions older APIs, but generate/OPZ still need a compatible core.