Pattern not being respected

danielen → changed the visibility of the branch 3473386-pattern-not-being to hidden.

I have a similar problem.

I've imported content via cron and the pattern is not respected. After manually saving the imported content, the pattern works.
I don't have this problem when I create a new node manually.

Same problem here. But when I open the node to edit and save again, the node title is generated properly.
As a workaround I now changed the settings to "Create label before first save".

Having the same issue as #4

We're seeing the same issue. Our pattern uses a single token that points to a text field on the same entity. That field allows some minimal formatting, but the generated labels are as described above (e.g. %AutoEntityLabel: 7a075eef-dde7-4c04-8f99-8f6a3f6e6177%) whether or not the field values contains formatting.

Re-saving the node corrects the generated label. Switching to the new 'Create label before first save' setting also works in our case.

No time to debug right now, but my assumption is this stems from changes in 🐛 Set Label runs two times on node creation Needs review .

Have the same issue. I'm using this in conjunction with 'Token OR' pattern and a node reference field 'Authors' set to 'Create referenced entities if they don't already exist'.

So if someone inputs a profile node in 'Authors' that doesn't exist, the entity is created, and for the title it first it looks if the name field is populated, if not it uses the auto generated title from 'Create referenced entities' and if neither of those work then it fills it with 'Unnamed profile' as a fallback.

If someone creates a profile node manually it takes the title from 'field_profile_name' which is a mandatory field.

My token for auto_entity label is:

[node:field_profile_name|node:title|"Unnamed profile"]

Not sure how to configure this to get it to work - had to roll back to 8.x-3.2.