Skip to main content
Table of Contents

Fix Out-of-Sync METRC Packages

Resolve METRC package sync errors in Flourish Software by clicking the out-of-sync icon and retrying. Learn how to identify sync status issues and get your inventory back in compliance.

Fix Out-of-Sync METRC Packages

Purpose

Resolve METRC package sync issues as soon as possible — an out-of-sync package can create compliance problems. In most cases you can re-sync a package yourself in a few clicks. This guide shows you how to spot an out-of-sync package, retry the sync, choose between Retry and Sync from METRC, find out why it went out of sync, and what to do if it still won't sync.

How to tell a package is out of sync

In Inventory > All Packages, an out-of-sync package shows a red Out of Sync icon (a red circle with an exclamation mark) in the SYNC STATUS column.

Retry the sync

This is the most common fix. It works once any underlying issue has been resolved (see Find out why it went out of sync, below).

  1. Click the red Out of Sync icon.
  2. Click Retry Sync.
  3. Note the prompt confirming the package was added to the syncing queue, then click Dismiss.
  4. Find the package again in the Inventory screen and verify its sync status shows a green check.

If it still isn't in sync, reach out to support (see below) with the package tag and facility.

See the interactive tutorial: How to Resync a Package

Retry vs. Sync from METRC

If the package was already created or updated in METRC, use Sync from METRC (the green circular-arrow button) instead of Retry.

For example, if tag 1234 is out of sync:

  • Retry — tries to create tag 1234 in METRC.
  • Sync from METRC — gets tag 1234 from METRC.
Find out why it went out of sync

In some cases you can re-sync immediately. In others, you need to fix the underlying issue first, then retry.

To see why a package went out of sync, click the red Out of Sync icon and read the Context information shown in the middle of the screen.

For example:

  1. Your API key is invalid.
  2. You create a package, and it goes out of sync.
  3. The Context displays a "User Not Authorized" message.
  4. Update the API key, then retry using the steps above.

See also: Retry Sync - Case of "User not Authorized", or How to retry sync — a case of invalid tag if the tag itself is the issue.

If it still won't sync
  • If you'd rather remove the package as if it had never been created, use the Undo Package button.
  • Otherwise, contact support:
    1. Email support@flourishsoftware.com or reach out via the Support portal.
    2. Copy and paste the ID of the out-of-sync package.
    3. If you have multiple facilities, include the relevant facility name.

We'll respond and resolve it with you. We may need to ask a few follow-up questions, but help is on the way.

If you made changes in METRC

When you create a package in Flourish and it successfully syncs into METRC, you can change that package to a new item/strain in METRC within 24 hours. Flourish updates the item/strain on the package the next time it's pulled from METRC on sync. If the package is an input or output package on a manufacturing run, Flourish updates the run.

The one exception: if the package is already allocated to an outbound order under a specific item and the item changes in METRC, you must remove the package from the order and re-run the sync to update the package.

How did we do?

Retry Sync - Case of "User not Authorized"

Contact