Inconsistent Forge Review Triggers for Unpublished Extensions

Hello FGU Team,

I am currently working on a couple of extensions on the Forge that are currently unpublished, and I’ve run into a strange inconsistency with how the review queue is being triggered. I’m hoping to get some clarity on how the backend workflow handles these updates.

Here is the behavior I am seeing:

• Extension A (Unpublished): If I modify only the text description (no code changes at all), the extension immediately enters the review process and gets stuck there for several days.
• Extension B (Unpublished): If I modify either the code or the text description, it updates instantly and does not enter the review queue.

Since both of these items are still unpublished drafts, I would expect their update behaviors to be identical.

Could you help me understand why a simple metadata/description update on one item triggers a multi-day manual review, while the other bypasses it completely? Is there a specific setting, keyword flag, or item status causing this discrepancy?

I want to make sure I am optimizing my workflow and not unnecessarily clogging up your review queue with simple text edits.

Thank you for your time and for all your hard work on the platform!

Best regards,
Henix

Hello Henix,

If an item is submitted, it goes into moderation. The same is true for images and builds for the same item. If an item appears solid and I don't have any concerns for future moderation, I will often mark it as Trusted so that future updates can go through automatically. I don't have a way to mark text as Trusted without making the images and builds trusted as well. My guess is that the images were approved for Extension B along with the text, so I marked the item as Trusted. If you have not created an image for Extension A yet, then it is still in moderation status.

For instance, Barbarian and Sorcerer were both updated on 2026-05-17 14:13:29 and they were both approved. While the text was approved, they have not been marked as Trusted items yet because they don't have any images.

Nothing should generally sit in the moderation queue for days. They should be approved or rejected within 24 hours of submission.

That said, you have built a pretty solid list of items that appear to be good products, so I went ahead and marked you as a Trusted crafter. You can maintain this status as long as you continue to produce products that don't require de-listing or get flagged for moderation by customers.

Thank you so much ddavison for the detailed explanation! That makes perfect sense, and I really appreciate you taking the time to clarify how the moderation queue handles text updates versus images behind the scenes.

Wow, thank you so much for granting me Trusted Crafter status! I am incredibly grateful for the trust and support.

Thank you also for checking on the Barbarian and Sorcerer automations and for all the hard work you do managing the Forge!

Best regards,
Henix

Thanks for being a part of the crafter community.

Another question since we are on the topic, how does the Forge backend handle listings? I did notice a small quirk with one of my items and wanted to ask about it.

I had an extension (AoE Spells Auto-Targeting & Upcast) where the page draft was originally created a while ago, but I only recently published it live. When looking at the main Forge listing, it seems to appear behind the other newly released items.

Is the sorting order on the Forge marketplace based on the original page creation date rather than the actual public release date? If so, is there a recommended workflow for older drafts to make sure they don't get buried when they finally go live, or should we just create a brand new item right before publishing?

Best regards,
Henix

On Manage Item, there is a Display Priority value that defaults to 255. You can adjust that to shift it on your crafter Item's page.

Otherwise, the sorts for the general search for customers is based on column headings (sort asc or desc), newest to oldest, oldest to newest, or recently updated. The middle two will be based on create date. The last will be based on update date.

Make sense, thank you so much for the explanation!