I have a rather strange problem, every now and then some jobs seem to lose their definition and do not pickup any of the data.
When we replay theses loads just changing the loadid, everything work as expected.
Please find below an example :
Initialize task detail is empty :
Best Answer
S
Stéphanie FOURRIER
said
over 1 year ago
Hello Beatrice,
this is a known behavior explained by a delete propagation that must have been set to "Restrict". A record was supposed to be deleted but the restriction stopped the process. This is documented here in our documentation :
Technically speaking, when a restrict is found, a new parameter PARAM_SKIP_ALL is added to the job, which causes the behavior that you described.
I hope this helped.
Stéphanie.
1 Comment
S
Stéphanie FOURRIER
said
over 1 year ago
Answer
Hello Beatrice,
this is a known behavior explained by a delete propagation that must have been set to "Restrict". A record was supposed to be deleted but the restriction stopped the process. This is documented here in our documentation :
Technically speaking, when a restrict is found, a new parameter PARAM_SKIP_ALL is added to the job, which causes the behavior that you described.
Béatrice INTHILITH
Hi,
I have a rather strange problem, every now and then some jobs seem to lose their definition and do not pickup any of the data.
When we replay theses loads just changing the loadid, everything work as expected.
Please find below an example :
Initialize task detail is empty :Hello Beatrice,
this is a known behavior explained by a delete propagation that must have been set to "Restrict". A record was supposed to be deleted but the restriction stopped the process. This is documented here in our documentation :
Technically speaking, when a restrict is found, a new parameter PARAM_SKIP_ALL is added to the job, which causes the behavior that you described.
I hope this helped.
Stéphanie.
Stéphanie FOURRIER
Hello Beatrice,
this is a known behavior explained by a delete propagation that must have been set to "Restrict". A record was supposed to be deleted but the restriction stopped the process. This is documented here in our documentation :
Technically speaking, when a restrict is found, a new parameter PARAM_SKIP_ALL is added to the job, which causes the behavior that you described.
I hope this helped.
Stéphanie.
-
Can we reset Matches and run again on match rule change or add a new match rule?
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
Prevent loads from replacing values overridden by users
-
Keep Melissa API calls under control during development
-
Existing records and match/merge changes in app builder
-
Where are Matching Details of User Merges (and splits)?
-
Is there any built in xDM functionality that allows you to report on data differences between two points in time?
-
Enrich existing records
See all 53 topics