Loading Term: Silent there

Created on 27 March 2024, 8 months ago
Updated 17 April 2024, 7 months ago

Problem/Motivation

I tried to load a term where my email template is stored. But the code went nowhere. I have "display a message" before and after this action. It prints a message before but stopped there. There is no error message, either.

Steps to reproduce

Action: Entity:load
Name of token: get_ad
Load entity from: Type and ID
Entity type: Taxonomy term
Entity ID: 3319 (I confirm it exits)
Entity: term

The message I display after this action is "started", just to see whether the code is still moving along. But it didn't show up.

The log message is:

Check action successor load term: email ad and signiture (Activity_1d58i41) from ECA 问诊单相关邮件 (process_g7cfnpf) for event Drupal\eca_content\Event\ContentEntityUpdate.
- entity (Entity node/visit/91475/03/26/2024 - 18:12)
- node (Entity node/visit/91475/03/26/2024 - 18:12)
- event (DTO)
- machine-name (string "eca.content_entity.update")
- view_list (DTO)
- ht_ad (Entity commerce_product/ht/136/汉唐-36 天青丸(妇女痛经) (兼治下身淤血、受伤))
- user (Entity user/1/家慧中医)

Not asserting condition Flow_1sif7oi for load term: email ad and signiture from ECA 问诊单相关邮件 (process_g7cfnpf) for event Drupal\eca_content\Event\ContentEntityUpdate.

Then stoped there.

Could you advise what I did wrong? Thank you!!!

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Fixed

Version

1.1

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @sdsc
  • 🇩🇪Germany jurgenhaas Gottmadingen

    The message Not asserting condition Flow_1sif7oi for load term means that there must be a condition applied to the arrow after the load entity action. And that condition is not true, that's why processing stops at that point.

  • There was no condition on the arrow. But I dropped that model and started new one. I used the same function still with no condition on arrow. It works now! Maybe some setup stuck in previous model.

    This ticket can be closed. Thank you!

  • Status changed to Fixed 8 months ago
  • 🇩🇪Germany jurgenhaas Gottmadingen

    OK, thanks for your feedback. What may have happened in the former model is, that the arrow used to have a condition and it got removed later on. This is sometimes not working correctly, a little glitch in the external bpmn_io library. An easy workaround then is to delete the arrow, and then add a fresh one. Glad it works with a brand new model though.

  • That was very likely what happened. Thank you for your tip!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024