CJA Connection: backfill failure explanation | Community
Skip to main content
March 4, 2024
Solved

CJA Connection: backfill failure explanation

  • March 4, 2024
  • 2 replies
  • 1753 views

Hi there, 

When creating a Connection on CJA, enabling backfill of data for my dataset, after processing the backfill I get a backfill status "backfills failed". 

Is it possible to get an error diagnostic for the failure? What could cause a backfill to fail? 

 

Thanks in advance, 

Liz

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Nirmal_Jose

Hi Liz,

 

the best possible place I can think of is going through audit log using [1]

 

[1] - https://developer.adobe.com/cja-apis/docs/endpoints/auditlogs/ 

2 replies

Nirmal_Jose
Adobe Employee
Nirmal_JoseAdobe EmployeeAccepted solution
Adobe Employee
March 9, 2024

Hi Liz,

 

the best possible place I can think of is going through audit log using [1]

 

[1] - https://developer.adobe.com/cja-apis/docs/endpoints/auditlogs/ 

March 3, 2025

Definitely look in the CJA logs (CJA > Tools > Audit Log). Filter to a date and email that initiated the backfill, once you find the particular component type for a backfill which will be "CONNECTION" in this case, click on the info icon on the right of the description for this particular line and copy the description in the popup. I had a similar issue like this and for some reason it showed as "backFillEnabled": false even though it wasn't which was causing our backfills to fail.

 

Thanks,

MJ

liz25Author
May 19, 2025

Hi MJ,

thanks for sharing your experience. I have another case of failed backfill for a dataset, and I'm trying out your technique. I don't have an info icon for the line, which API client are you using? 

thanks, 

Liz

May 21, 2025

An update: I've reviewed my set-up and everything seemed to be in place technically, so I've just requested the backfill again, and it worked. 

So it could be that for the first backfill failed for technical reasons on Adobe's side, and running it at a different date and time just worked. Something to have in mind as well. 

/Liz


That's good news. Sometimes ingestion fails and does need to just be re-ingested.