There is a limitation in the v1 version of the zrok agent that when a share or access it is managing encounters an error, the share/access is removed from the agent… it has no notion of a share or access process in an “error” state, and no mechanism for retries.
We’ve soft-launched the new v2 version of zrok in production on zrok.io. The new v2 agent fully supports errored shares and handles retries.
Some of the semantics of how things work in v2 are different… specifically, reserved shares are handled in a completely new way.
There is a video available that demonstrates the new v2 features:
