Skip to main content
Developer Communities Admin
Community Manager
September 15, 2026

I have set up a few outbound integrations and this past week or so they have been failing with the following error :

  • September 15, 2026
  • 3 replies
  • 0 views

Originally posted by Jeff Dooley on January 2, 2026 at 10:09 AM.

 

Hello everyone,

 

I have set up a few outbound integrations and this past week or so they have been failing with the following error :

 

{

 "TaskId": "e15e711a-9408-4ca9-a636-456e6cc7a44a",

 "Name": "RetrieveDayforceApiTask",

 "StatusType": "Failed",

 "Diagnostic": {

  "Message": "FailedToRetrieveData: Request failed.",

  "ErrorCode": 3,

  "ExceptionProperties": {

   "HttpStatusCode": "BadRequest",

   "HttpStatusCodeInt": "400",

   "BenefitsAPI_Carrier_Feed_Export_Error": "Run Dayforce Link Export failed due to an Exception: The employee records should be 50, but there are 49 loaded. Bad employee data found:[88733]",

   "IsRetryable": "False"

  }

 }

}

 

It seems to be related to something bad about an employee’s (or employees) data in the database. If you try to find the employee with the specified id in the Dayforce application you cannot find them, they do not appear in the Profile or other modules. In many cases if you re-run the integration the next day the error goes away.  Does anyone know if there are any ways to prevent from happening or possibly correct the employee data within the Dayforce application itself?

    3 replies

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Eddie Heinzelman on Jan 2, 2026, 10:18 AM.

     

    Jeff,

    I'm pretty sure this error is employee data related, and agree, it can be difficult to locate, especially when looking for data that isn't there. Things to check are anyone who was possibly a Pre-Start employee who might have also Terminated or didn't go Active status but has an open/active Benefit Record, or also make sure they have an address which may be missing. Since this worked previously, start with anyone who is newly added to Benefits for troubleshooting.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Brenda Sutton on Jan 2, 2026, 10:33 AM.

     

    Hi @Jeff Dooley​, I agree with Eddie. This is very common when there is "bad" data in the customer instance. Typically, there is something missing for the employee(s) that is later corrected.... that's why you are getting the error then it resolves. Here is a KB article that may help you as well: https://dayforce.lightning.force.com/lightning/r/Knowledge__kav/ka25d000000bsqoAAA/view. If you can't access let me know and I will post the details.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Jeff Dooley on Jan 2, 2026, 10:46 AM.

     

    Thank you Eddie and Brenda for the quick responses! I can access that KB article, I will review and see what can be done to fix the employee.