I can see you are attempting to perform an HTTP API update to a profile record.  xdmEntityUpdate is indication you are attempting to perform an upSert.  xdmEntity will use activity to write data upon a dataSet.   Are you attempting to write data upon a profile or experience dataSet?

Hello @MerinKumar    You can use the following as refresh to obtain the GCP refresh token   https://developers.google.com/identity/protocols/oauth2/native-app?hl=en#offline

At this time parquet is only XDM compliant.  You have more flexibility if the data in in json to create a mapping flow.

Hello @arpan-garg    I thought this was the case as well, but when I change the batch scheduler to execute the composite audience was not evaluated.     I think this is out side of the UPS batch scheduler as AO audiences are outside of the UPS node of a profile.

Description - Ability to map in non XDM compliant parquet files Why is this feature important to you - Source systems are not always producing parquet files which are xdm compliant How would you like the feature to work - Ability to map in parquet files from cloud based source connectors. Current B...