Pending States - Introduction
Previously, if your inventory package received a failed API from Metrc upon creation, there was no indication of who, what, or why the package failed the API call. Now, your inventory package received a failed API from Metrc upon creation, the “Pending State” tools will clearly indicate the reason for the failed call, and from where the error originated:
With this knowledge, we can now more easily identify and more quickly resolve these issues.
These tools include:
Auto-corrections
Pending States identifier
MJ Platform now gives you the option to enable a tool for your inventory, which helps identity and prevent failed API calls when creating a package in Metrc. This tool will help to automatically correct the issue when possible, and also provide more useful insight and guidance as to why there was a failed API to Metrc when you created a package, and better equip our team for monitoring and addressing these items.
Auto-corrections
Pending states
Issues that are addressed with Pending States
Prevent Type 2 Missing Tracking ID’s:
“Type 2” describes a child package of a “Type 1” inventory package.
For example: You create a package, and it does not make a successful call to Metrc, which results in your package missing a Tracking ID. You then split that package 100 times using the “Split Package” tool, which results in 100 more failed API calls, and also 100 additional packages that are missing a Tracking ID, plus the parent “Type 1” package.
We’re going to prevent this issue so we can minimize the impact on your inventory tracking in your system and your compliance reporting.
Help prevent Type 1 Missing Tracking ID’s:
Type 1 describes an inventory package that was not successfully sent to Metrc upon creation, and does not get assigned a Tracking ID upon creation.
For example: When you create an inventory lot/package from a harvest, or when you create an Inventory Receipt through the Supply Chain.
Faster resolution by quickly identifying the reason for the missing Tracking ID:
If a created package is not successfully sent to Metrc, and then results ina missing a Tracking ID, then the system will provide a button/modal for each package, which provides detailed information on why the item did not send a successful API call to Metrc, and how to proceed for resolution.
How does it work?
First, you have the option to enable the setting in your facility. This is a toggle that you can turn on, located on the “Inventory Compliance” page in your Advanced Settings
Second - Auto-Corrections:
When a package is created in your facility, but the API call to Metrc fails due to server or timeout issues, then the system will automatically, and silently, make attempt to retrieve the Tracking ID again for a specified interval of time.
When a successful call is made, then the package will be available for use as expected.
When auto-corrections tool is unable to retrieve the Tracking ID, then the package is placed into a “pending state” which helps clarify the reason for the missing Tracking ID, aiding in faster resolution identification and resolution for this package.
Third - Pending State:
When you create an inventory package, but the API call to Metrc is not successful, the “Pending states” feature will place the inventory package into a pending, or temporarily disabled state.
This ensures that you cannot expand the issues by preventing actions that will result in more failed API calls to Metrc, and more items without properly assign Tracking ID’s.
The package with the missing tracking ID will display a unique icon that that identifies
Likewise, our team has an intelligent new Dashboard and set of internal tools to monitor, identify, and help resolve these issues with greater accuracy and speed, while preventing further missing Tracking IDs (Type 2).