MJ Platform Errors

Error message

Context

Cause and Solution

Package Split Cannot Proceed: The item, <item name>, is not in your list of Metrc items. Please double check your list of items in Metrc or ensure that the spelling of the item in MJ Platform matches the spelling of that item in Metrc.

Trying to split a package in a Metrc-integrated facility.

Either the item hasn’t been pushed to Metrc yet, or the spelling of the item in Metrc is slightly different than in MJ Platform. Log into Metrc and manually update the item name so that it matches MJ Platform exactly.

Additionally, check your API key to ensure it is correct.

You must set up EA package sizes for this facility.

In a Metrc-integrated facility, trying to move Bulk inventory to a Category that only supports EA unit of measure (not GR with Prepacks) during a packaging job.

Make sure the product master's unit of measure is set to EA.

Check that the vendor name in the product master is spelled exactly the same as it should be. Check for uppercase/lowercase and trailing spaces.

Check that package sizes are set up correctly.

The Quantity defined exceeds Weigh on Hand Margin of Error

Trying to sell a cannabis product

Cause 1

The sales setting “Margin of Error” is lower than the amount to be sold. Ensure the amount sold is closer to the actual decrease in inventory, or change the margin of error setting to accommodate higher discrepancies.

Cause 2

The inventory amount is negative. Contact support so that they can set the quantity to zero.

Failed to get x

(Where x is any entity such as prepack weights, vehicles, partners, drivers, etc.)

Modifying a Transfer or creating a Purchase Order

Wait a few minutes and try again. If the problem persists, contact support.

Your Leaf integration was disabled at <time> and returned to setup mode due to invalid credentials. Please check your integration settings.

Appears as a priority notification (popup modal).

In a Pennsylvania facility, if it is taken out of setup mode but automatically goes back into setup mode.

If your integration was working before and suddenly starts failing, it is possible that an administrator changed your integration API key or inactivated the account of the API key holder.

See here for troubleshooting details.

Leaf cannot be activated due to current medicated, but unlinked, inventory in the system.

In a Pennsylvania facility, if it is taken out of setup mode but automatically goes back into setup mode.

Contact support and inform them of the error message.

This username has already been taken.

Trying to save a new user account and there isn’t already a user with that username.

The username was taken by another facility or organization using MJ Platform. You cannot use the same name because the username is linked to their organization. Choose a different username.

METRC error:

Facility can not sell to External Patients.

Trying to finish an order for an out-of-state patient in California.

In California, out-of-state patients require an ID method to be selected in their patient profile so that MJ Platform can send it to Metrc when the patient makes a purchase.

Unhandled Exception - window.askNicelyConversation is not a function.

Attempting to download reports.

There may be a temporary internal server error. Wait a few minutes and try again. If the problem persists, contact support.

Rewards not enabled

On the patient profile and/or completed transaction.

The patient is not in one of the patient groups eligible for rewards. Go to Rewards Setup and under Reward Constraints, in the Points earned in the following patient groups field, either select the group that the patient is in or deselect all of them to allow rewards for all patients.

422 Validation Error For At
/api/leaf/oracle/sync_patient
_to_platform

Clicking the Sync button trying to manually add an MMID card to a patient profile in Pennsylvania.

Possibilities:

They will need to resolve these issues before they can purchase medicated products.

The name has already been taken

Trying to create a new Sales Order.

Create an Accounts Payable/Accounts Receivable register.

Packaging job completion failed

Trying to complete a packaging job.

This may happen if the product masters involved were created less than 2 hours before the error appeared. Wait 2 hours and try again. During this time, check the API log and check the details of the failed call. If the error says "The output from this packaging job is not a valid output for the input type" then the category of the product master was one that was previously mapped as byproduct. Due to Utah regulations, the product master can never be used again even if its category is changed. Create a new product master and inventory, and adjust its quantity to the appropriate level.

Make sure that driver user State Integration ID is set

Trying to save a driver profile, or trying to complete a supply chain operation with that driver.

Modify the driver's profile. From the Select User drop-down menu, select an active user to be the driver. This links the driver account to a user which automatically has an ID for the state integration.

Patient is part of a restricted study

Trying to check in a patient in Pennsylvania

check-in troubleshooting

Not enough inventory to complete order

Trying to add items to a cart or fulfill

It may be the case that certain packages are stuck "in reserve". See these troubleshooting steps.

There is an existing inventory receipt for the specified purchase order.

This is applicable to users in Utah:

Clicking Save after mapping a Purchase Order.

Contact support to escalate the issue.

SoloTag Error.

Trying to activate SoloTags for plants in the Solo app in Utah.

Modify your user profile in MJ Platform and click Generate New Key. Save, then input it into the app.

If the problem persists, try reinstalling the app.