Troubleshoot Metrc Sync in Flourish: Overview

Every time you create or update a compliance record at a Metrc facility, Flourish sends the change to Metrc. If Metrc doesn't accept it, the record shows as Out of Sync. Flourish and Metrc no longer match until you fix the cause and retry.

Fix out-of-sync records as soon as you see them. Until they're fixed, your Metrc data is incomplete, and records that depend on them can fail too.

This applies to Metrc facilities only.

Spot an Out-of-Sync Record

Lists that sync to Metrc have a Sync Status column. An out-of-sync record shows a red icon:

Red out-of-sync icon shown in the Sync Status column.

Click the icon to open Sync Status Detail. It shows the action that failed, the result, and a Context message from Metrc explaining why. Read the Context message first; it usually tells you what to fix.

Flourish may add a plain-language hint after Metrc's message, such as which Metrc permission is missing. The hint appears on records that went out of sync earlier, too.

Status	What it means
In Sync	Metrc accepted the latest change.
Not Yet Synced	The record hasn't been sent to Metrc yet. Harvests stay here until you sync them.
Out of Sync	Metrc rejected the latest change.
Partial Sync	Harvests only. Metrc recorded some of the plants but not all.

Fix It by Record Type

Record	Where to retry	Guide
Strain	Settings > Inventory > Strains, then the strain's Compliance tab	Re-Sync an Out-of-Sync Strain in Metrc
Item	Settings > Inventory, then the item's State Eligibility	Fix an Out-of-Sync Item
Package	Inventory > All Packages	Fix Out-of-Sync Metrc Packages
Immature plant batch	Grow > Propagation	Fix an Out-of-Sync Plant Batch in Metrc
Vegetation, Mother, or Flowering plants	Grow, then the plants view for the stage	Retry Sync for Out-of-Sync Plants in Metrc
Harvest	The harvest log, then Sync Harvest	Retry Harvest Sync in Metrc
Retail order	Retail > Purchases > All Purchases	Fix an Out-of-Sync Retail Order

Fix records in order. Packages and plants depend on items and strains. If several records are out of sync, fix the strain first, then the item, then the packages or plants that use them. Retrying a package before its item is in sync will fail again.

Common Causes

What the Context message says	What to do
The credentials stored in Flourish for this user are invalid, or the user lacks the permissions needed for the action (Metrc rejected the request as unauthorized) [VERIFY: confirm the final message wording in production]	Metrc returns this one message for three different causes. Check them in this order: 1. The key isn't valid for this license. The API key may be valid for your other licenses but not the one you're syncing to. See Fix Invalid Metrc API Key in Flourish. 2. The key is valid, but the user lacks a permission. The hint names the permissions needed for the action that failed, such as Manage Items. Enable them in Metrc, then retry. See Configure Metrc User Permissions for Flourish Sync and Retry Sync: User Not Authorized. 3. The package was transferred to a different license. Metrc returns this message for package lookups on a package that now belongs to another license, no matter which key or permissions you have. Changing the key or permissions won't fix it. [VERIFY: what the user should do in this case]
Tag is not valid	The tag is already used or isn't active in Metrc. Pick a different tag and retry. See Retry Sync: Invalid Tag.
New Package: Content Package cannot be used because it is part of an existing Transfer	An input package for the new package is already on a transfer in Metrc. Free it from the transfer, then click Retry Sync on the new package. See Fix Out-of-Sync Metrc Packages.
Strain or item does not exist in the current facility	Sync the strain or item to that facility first, then retry the record that uses it.
Location is invalid	The area isn't mapped to a Metrc location that allows the action. Update the area's Metrc location, then retry.
Timeout, or Metrc service unavailable	Metrc was slow or down. Wait a few minutes and retry. Large plant moves and harvests are the most likely to time out.

Retry or Sync from Metrc?

Choose based on which system has the correct data:

Retry Sync sends Flourish's version to Metrc. Use it when the change was made in Flourish and Metrc didn't take it.
Sync from Metrc pulls Metrc's version into Flourish. Use it when the change was already made directly in Metrc. See Sync Changes Made in Metrc Back to Flourish for cultivation records, and Fix Out-of-Sync Metrc Packages for packages.

If a change was made in Metrc, don't retry from Flourish. The retry resends the original action, and Metrc will reject it again or create a duplicate.

Still Out of Sync?

Contact Flourish Support at support@flourishsoftware.com or through the Support portal. See Support. Include:

The record: package tag, plant ID, harvest name, item name, strain name, or order number
The facility name, if you have more than one
The Context message from Sync Status Detail, or a screenshot of it