That's right. If another ingestion flow is actively writing to the same dataset/fields around the same time that a Journey updates them, the final field value may reflect the most recent ingestion rather than the Journey update. It is recommended to configure a dedicated dataset (with required attributes) for Journey-based updates or ensuring that no conflicting data ingestion overwrites these fields.