Order design cannot be generated
There are cases when you will find that the Order Design is not rendered inside your Order Page.

There might be a lot of reasons for this issue. In this article, we will guide you through each case and how to resolve it.

Continue reading to find each case and how to resolve it below.
CASE 1. No query results for model [App\ArtworkVersion]

Reason: Outdated Artwork version. This can potentially happen when you update the Artwork on an on-going Campaign, and the order was created with an outdated artwork version.

CASE 2. Line item cannot generate design File not found at path: .../fonts/...

Reason: The Custom Font you are using have been deleted.
CASE 3. Line item cannot generate -- find not found at path: .../cliparts/...

Reason: The particular Clipart the Customer chose had been deleted.
CASE 4. Order design cannot be generated because no artwork found for the selected printarea

REASON 1 - No Artwork selected for the Printarea.


REASON 2 - The Artwork or Product Base was removed from the Campaign after the order was placed.
If the order log shows Cannot generate design because no artwork found, use Recover design to generate the file from the customization data saved with the order. Recovery uses the original Artwork snapshot, not the Campaign's current Artwork. This applies to both Campaigns by Product Base and Campaigns by Shopify Products.
Recover the order design
- Go to Teeinblue Portal > Orders > open the affected order > Item Activity logs. Find the latest no artwork found failure for the affected item.

Example of the error and the Item Activity logs button. The recovery confirmation is described in the next step.
- In Teeinblue Portal > Orders > open the affected order > Item Activity logs > Recover design, click Recover design on the failure entry and read the Recover this design? dialog. Click Recover design to confirm, or Cancel to leave the order unchanged.
- In Teeinblue Portal > Orders > open the affected order, wait for the recovered design to finish generating. Check the customer's personalization, file dimensions, and aspect ratio before fulfillment.
Which size does the recovered file use?
- Campaigns by Product Base, with the original Printarea still available: the file uses the original Printarea size and retains its fulfillment mapping. You can fulfill the order as usual after checking the file.
- Campaigns by Product Base, with the original Printarea no longer available: the file uses the ordered Artwork version's size without a Printarea key. This can happen after the removed Printarea data is permanently cleared after 30 days. Check the file and fulfill manually, as described in the warning above.
- Campaigns by Shopify Products: the file uses the Artwork size, as it normally does for this Campaign type. This is not the missing-Printarea fallback.
If you already uploaded a custom design
You can still recover the Campaign design. Your uploaded file stays alongside the recovered design; recovery does not replace it. Check both files and choose the correct design for fulfillment.
If recovery is unavailable
- You need permission to manage orders to see Recover design.
- If the item already has a generated design, use Re-generate instead of recovery. Re-generating a recovered design uses its recovered Artwork snapshot.
- If the required Artwork data is no longer available, recovery cannot rebuild the file. Contact contact@teeinblue.com for help.
- If you added a new Printarea or changed the Product Base and the error is not caused by a removed Artwork or Product Base, contact support to check the mapping. Update the Campaign after making changes.
CASE 5. Order doesn't have design & Customization_id is empty

Reason: There might be a conflict between the application and your Theme which makes the customization data is not recorded.
CASE 6. Line item cannot generate design unable to extend cache '': File too large @ error/cache.c/OpenPixelCache/3900

Reason: Artwork Layers is way too large, overlapping its actual size.

CASE 7. App\Jobs\GenerateOrderItemArtwork has been attempted too many times or run too long. The job may have previously timed out.

Reason: The order might accidentally stuck on our queue system.
12000 x 12000 pxUpdated on: 26/09/2026
Thank you!
