ACS Error “Unable to extract {0}” after 3 successful attempts.

I have a filepath, event, and subscriber configured identically to other successful ACS subscribers, but every time, I get 3 successful transfers and then the Unable to extract {0} error. I made sure to assign read privileges for everything the subscriber would see. This is a new subclass that we are exporting though, is there anything about the data itself that could cause the error? I opened every single item on the first failed transmission and nothing appeared wrong.

Agile User Asked on August 6, 2021 in Other APIs.
Add Comment
1 Answer(s)


In order to find out the root cause, you have to check the STDOUT log. By the way, is your environment clustered or non-clustered? If clustered, I hope ACS is running on only one node, please check once.

Coming back to the log checks,  from the Web Client’s Tools Menu –> Administration –> Logging Configuration, set the following loggers (if you are using 9.3.6 with Log4j 2.X) or categories (if you are using log4j 1.2.X)


Now when your 4th ATO fails with the error, keep a monitor of the STDOUT log and see what exception is being thrown, from there you can have an idea what is actually disrupting the extract.

Are you able to see any other indicative errors in the ATO/CTOs’ Where Sent tab’s Transmission Notes cell?

Agile Expert Answered on August 6, 2021.

Thank you for your reply. I did some more testing of this and it turns out it’s related to some workflows that we broke during a domain and userid migration. I’ve posted about that issue before, and we’ve still not been able to correct the problem. A handful of items from before our migration are not accessible and return a nullpointer error when you try to view the workflow tab.  Even if it’s only one out of a thousand object that I include in my ATO criteria it will still fail a transfer. A solution to the userid breakage would be the best thing ever, but for now I have all of the old data in a pre-migrated instance that I can pull from .

on August 18, 2021.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.