Find the next safe step.

This indicates a missing application loader dependency. Close Workbench and use the official complete installer or your IT-approved repair package. Repair the supported Microsoft WebView2 Runtime as directed by the installation guide. The package must include the correct loader for its architecture; a runtime installation alone cannot replace a missing bundled loader. Do not download DLL files from third-party DLL sites.

Check the exact version, download channel and publisher with IT. The current preview.3 direct installer is publicly signed for vSecure Solutions LLC. Its installed app and uninstaller signatures passed native Windows verification. Keep protections enabled and report any warning with the file hash; a valid signature does not guarantee every device’s reputation or policy acceptance. Legacy 2.2.2 files are different downloads.

In the evaluated build, the supported Operator connection reuses verified Hub identity and checks current service rights. Confirm the account and entitlement, then reconnect that service. An expired session, an explicit previous disconnect or an older installed build can need attention. Do not put your password into a support message. Provider OAuth consent and the CLI’s device authorisation remain separate.

Check that your installed build includes Private workflows and the approved local component. Read the readiness message: supported CPU, memory headroom and isolation checks must pass. Close unneeded applications if policy permits and try again. A failed check blocks private processing; there is no automatic cloud fallback. Give support only the sanitised error code and version, not the private source.

Check connectivity, sign-in and service access. A capacity message can mean the planning service is busy. Try a fresh plan later, or reuse a genuinely verified plan while it remains valid. Its original generation date stays visible; validity is seven days. An offline device cannot fetch a fresh plan. Do not paste the source into standard cloud chat as a workaround.

Use supported UTF-8 text, Markdown, CSV or TSV and a focused, permitted extract. The input file limit is 1 MiB; private AI has the smaller source/question/context limits listed in the product guide. A short answer is expected under the bounded output budget. Use an approved local conversion for unsupported formats, never an unapproved online converter for confidential material.

Check the result against its source before using it. Stop cancels current inference; changing the input invalidates the old answer. Choose an approved local destination for exports and check sync and backup policy. Clearing the working view does not delete exported files or provide forensic erasure. No AI answer is an automatic administrative decision.

In Operator, open the publication details and check the platform account, authorised route, provider permissions and error. Connection status is not a publication receipt. Retry only a job known to have failed before submission; reconcile uncertain submissions before retrying to avoid duplicates. A local worker needs the device awake and online. These online publishing routes are separate from private document processing.