Introduction
Some nodes require specific fields in the target to function correctly.
A necessary field missing
Send by contract node
This node requires the presence of the numberly_contract_id field in the queryly segment to function. It allows one email to be sent per contract chosen for each of the individuals in the segment.
There are two ways to check for the presence of the field in the queryly segment:
From the journey execution tab, when hovering over the queryly node, three small dots will appear; click on them and a new window will appear. The segment can be viewed at this point.
From the segment customization page on Queryly
Distribution node by customization field
This node requires the presence of the fields requested for the distribution conditions within the Queryly segment.
The possible checks are identical to those detailed for the node above.
The case of the field must be respected.
Splitting node according to segment membership
This node requires that the primary key of the splitting segment be present in the input segment of the journey.
An error may occur if the segment uniqueness key is not the same between the journey input segment and in the separation node.
- If the separation segment has one row per contract, (deduplication to contract has been disabled on queryly), then the population entering the node will be separated according to the contract identifier. This field must therefore be present in the incoming population. This field must be named
contract_numberly_contract_id.
Conclusion
Once this alert has been lifted, execution can be restarted