In Diskussion Workflow Error While Automating Game Update Notifications

[Hande]

Hi everyone,
I've been testing JTL Workflows with product imports from an external source. The products are related to gaming apps/mod files, and I noticed that the workflow doesn't always trigger when new items are synced.

For example:

• Imported product has all fields (title, description, SKU).
• Workflow condition set to trigger when a new product is created.
• But sometimes the workflow doesn't execute, especially when data comes from CSV/API imports.

Has anyone faced this issue before? Do I need an additional condition (e.g., status update or attribute field) to make sure the workflow always triggers?
Thanks in advance for your help!

 

[Björn Ponsen]

Guten morgen,

es wäre super, wenn du hier einmal deinen Workflow postest, damit man sich ein genaues Bild davon machen kann, wie dein Workflow aufgebaut ist.

 

[Hande]

Hi everyone,
I've been testing JTL Workflows with product imports from an external source. The products are related to gaming apps/mod files, and I noticed that the workflow doesn't always trigger when new items are synced.

For example:

• Imported product has all fields (title, description, SKU).
• Workflow condition set to trigger when a new product is created.
• But sometimes the workflow doesn't execute, especially when data comes from CSV/API imports.

Has anyone faced this issue before? Do I need an additional condition (e.g., status update or attribute field) to make sure the workflow always triggers?
Thanks in advance for your help!

I’ve faced something similar before — JTL Workflows sometimes skip triggers when data is imported via API or CSV because the system doesn’t always register those as “manual” creations.


One workaround that helped me was adding an extra condition, like “Product active status = Yes” or a custom attribute update step right after import. That small change usually forces the workflow to detect the new entry.


I actually ran into this while setting up product syncs for gaming apps like nullsbrawll — and tweaking the trigger conditions fixed it.


Try testing with one product first and check if the workflow logs record it properly.