in Integration Studio for an outbound integration when using the Benefits Carrier Feed API occasionally the scheduled integration job fatally fails with an error like:

Originally replied by Pranaw Sharma on Aug 6, 2026, 3:20 PM.

Hi Jeff, Yes, this can be done by applying a filter at the root level in the Mapping step of the integration. By filtering at the root, you can exclude specific employees from being included in the outbound payload, allowing the integration to continue processing the remaining employees.

That said, this approach can create an ongoing cycle of adding employees to the filter when issues occur and then removing them later once the data has been corrected. It also introduces a maintenance consideration—if one user adds an employee to the filter and another user is unaware of it, it may appear as though the Benefits Connector is not functioning correctly because the employee is unexpectedly missing from the outbound feed.

For that reason, while filtering is a viable workaround for exceptional cases, it's generally recommended to resolve the underlying employee data issue where possible to keep the integration behavior predictable and the outbound feed complete.

Originally replied by Jeff Dooley on Aug 6, 2026, 4:45 PM.

Thank you for the suggestion Pranaw. That would be helpful to send the file. Unfortunately I am finding an employee who is not visible in the Employee Profile or any admin screens in the Dayforce UI. I tried to add a root level filter based on the id in the error message using Employee Number and Employee XRef Code but still got the same error. It seems in this case the employee needs to be fixed in the backend due to their bad data?

Originally replied by Pranaw Sharma on Aug 10, 2026, 9:25 AM.

Hi Jeff, What kind of bad data does this employee have?

Based on your description, it's possible that the data processor is encountering the invalid employee record and failing before the root-level filter is applied. If that's the case, the filter wouldn't have a chance to exclude the employee from processing.

If the employee is not visible in the Dayforce UI or any admin screens, it does sound like there may be an underlying data issue that needs to be investigated and corrected in the backend. If you can share more details about the bad data or the employee record, that may help determine whether this is indeed the cause.

Originally replied by Jeff Dooley on Aug 26, 2026, 10:37 AM.

Hi @Pranaw Sharma​ I am sorry for the delayed response. I could not find this employee in the UI or admin screens. I do not have backend access to this instance so we created a ticket and support was able to correct in the backend via SQL. I created an enhancement AHA Idea (https://dayforcestaff.ideas.aha.io/ideas/BENEFITS-I-1307) to see if the API can fail with warnings for these cases and skip the bad employee.