Overview: Why We Use This Feature
Canix helps to avoid errors by automatically reserving Package tags when you are working on creating new Packages. This feature avoids issues with other users accidentally using these tags before your work is completed. When a Package tag is reserved, it enters the Unsubmitted status. These can be cleared out as needed to restore availability of these tags for use with Package creation.
Unsubmitted Packages are in a draft state and have not yet been created as valid or usable Packages — the tags are simply reserved for use. Reserving the tag at the start of the workflow protects it while work is in progress; deleting the Unsubmitted Package un-reserves the tag rather than deleting a real Package.
Glossary
- Package Tag: The unique tag (e.g., 1A4FF0300000123400000001) assigned to a Package.
- Unsubmitted (status): The status a Package tag enters when it has been reserved by an in-progress, pending, or failed Package creation workflow. The Package is in a draft state and is not yet a valid or usable Package.
- Available (status): A Package tag that is free to be used for Package creation.
- Pending Approval Submission: A submission awaiting Admin approval before the Packages are created.
- Failed Submission: A submission that did not process successfully; viewable on the User Submissions or Metrc Submissions page with an error message.
- Delete Packages: The action used on Unsubmitted Packages to un-reserve the tags and restore them to Available.
Prerequisites & Setup
Before beginning, ensure the following requirements are met:
- Permissions: Access to Inventory > Packages in the Canix Web Application. Admin permissions are required to approve a Pending Approval Submission.
- Necessary Data: One or more Package tags currently in Unsubmitted status.
- Related Resources: For more information on Package Statuses, please see Package Availability Status.
Step-by-Step Instructions
Follow these steps or watch the demo video to complete the workflow.
- Access the Module: Navigate to Inventory > Packages > View: Unsubmitted.
-
Select the Tags: Select the Package tags you wish to restore to Available for use.
- We suggest using filters to narrow your search if needed.
- You can reference the Packaged Date column to see when the workflow was started or submitted to try creating this package.
- Select the Package tags individually, or in bulk by selecting the first consecutive package tag and then holding shift when selecting the last consecutive tag.
- Optionally, restore all Unsubmitted Package tags by not selecting any tags, which will default to including all tags.
- Initiate Action: Select Actions > Delete Packages.
- Review & Confirm: In the new confirmation window, confirm you would like these un-reserved by selecting Delete.
Your previously Unsubmitted Package Tags are once again available for use, and you can return to creating new Packages with them.
Important Considerations
These "pro-tips" and warnings help avoid common pitfalls:
- If no tags are selected in the Unsubmitted view, the action defaults to including all Unsubmitted tags — confirm your selection before deleting.
- "Delete Packages" on an Unsubmitted Package does not delete a real Package; it releases the reserved tag back to Available. Unsubmitted Packages are drafts and have not yet been created as valid or usable Packages.
- Before restoring tags from a Failed Submission, review the error message first so you don't repeat the same error on your next attempt. Use the Packaged Date column and filters to identify stale or abandoned workflows.
System Impacts & Dependencies
Changing data in one area often triggers updates elsewhere. Understanding these relationships is critical for data integrity.
| Action Taken | Impacted Area | Description of Change |
|---|---|---|
| Starting a Package creation workflow | Package Tag Availability | The Package tag is automatically reserved and enters Unsubmitted status, preventing other users from using it. |
| Deleting an Unsubmitted Package | Package Tag Availability | The tag is un-reserved and returns to Available for use in Package creation. |
| Admin approves a Pending Approval Submission | Packages / Inventory | The reserved tags are used to create the Packages, moving them out of Unsubmitted status. |
| A submission fails | User Submissions / Metrc Submissions | The tags remain Unsubmitted and an error message is recorded for review on the Submissions page. |
Troubleshooting Common Issues
If you encounter an error, check these common scenarios before contacting support.
- "Tag ... is already in use" error: If you are trying to create new Packages and some or all of the new tags to be used are in Unsubmitted status, you will receive the Canix error message Tag 1A4FF0300000123400000001 is already in use. Follow the steps above to restore those tags to Available, then try again.
- Package Tags on a Pending Approval Submission: Resolve by having an Admin approve the Pending Approval Submission to create them.
- Package Tags on a Failed Submission: Resolve by navigating to Admin > User Submissions or Metrc Submissions page, then find the Failed Submission and select it to view the error message for context on why it failed. This error message will provide the clear reason why it was not successful so that you can either retry it if there was no real error, or start over to create a new submission without the same error — if the latter, follow the steps above to first restore the Unsubmitted Package Tags to Available before trying again.
- Package Tags on abandoned or incomplete workflows: This occurs if you or someone on your team was working on creating new Packages but did not complete the workflow entirely, abandoned it without cancelling, or is still in progress. Resolve by following the steps above to restore the Unsubmitted Package Tags to Available before trying again.
For further assistance, please join our Office Hours.