Canix Package Availability Status Stays Unverified, Needs Review, or Transfer Pending

- A package shows Unverified and cannot be trusted for downstream activity yet. - A package remains in Needs Review and staff are unsure whether it can be sold or transferred. - Transfer Pending or Transfer Accepted appears and the team does not know which system should be used next.

- The state system has not yet sent status back after receive or package activity. - The package was flagged for review because a required field or compliance state does not line up. - The package is tied to an outgoing or completed transfer that must be managed in Metrc.

Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

- If the package was just received or created, allow the expected sync time before assuming failure. - For Needs Review, compare package details against finished-good, testing, and transfer requirements before making any new movement. - For Transfer Pending or Transfer Accepted, complete the related transfer workflow in Metrc, then refresh Canix. - Do not sell, relabel, or re-transfer a package until its status supports the intended activity.