Is anyone else seeing issuing in their test environment following the upgrade to 2026.1?
Originally posted by Jeff Dooley on March 2, 2026 at 10:26 AM.
Is anyone else seeing issuing in their test environment following the upgrade to 2026.1? I have an integration that was working successfully prior to the upgrade, but it is now failing consistently after the instance was upgraded.
"Diagnostic": {
"Message": "FailedToRetrieveData: Request failed.",
"ErrorCode": 5,
"ExceptionProperties": {
"DayforceBenefitsApiJobId": "08e1ea9f-8ee3-4672-baf1-b3c39eea3580",
"HttpStatusCode": "InternalServerError",
"HttpStatusCodeInt": "500",
"HttpResponseContent": "{\"requestId\":\"39f627be-a265-4fe9-b1d2-aea44c00f112\",\"processResults\":[{\"code\":\"SYS_FAIL\",\"level\":\"ERROR\",\"message\":\"Internal server error encountered while processing the following request: https://ustest261.dayforcehcm.com/api/xyz/v1/BenefitsCarrierFeedExportStatus?jobId=08e1ea9f-8ee3-4672-baf1-b3c39eea3580\",\"details\":{}}]}",
"Request": "api/xyz/v1/BenefitsCarrierFeedExportStatus?jobId=08e1ea9f-8ee3-4672-baf1-b3c39eea3580",
"RetryCount": "5",
"SYS_FAIL": "Internal server error encountered while processing the following request: https://ustest261.dayforcehcm.com/api/xyz/v1/BenefitsCarrierFeedExportStatus?jobId=08e1ea9f-8ee3-4672-baf1-b3c39eea3580",
"ErrorStackTrace": "DFIntegrationPlatformService.Application.ApplicationException`1[DFIntegrationPlatformService.Application.Retrieve.Dayforce.QueueDayforceBenefitsApiErrorCodes]: Request failed.",
"IsRetryable": "False"
}
},
It now always fails on that step where it used to run successfully. I’ve noticed that the REST API endpoint is using a URL with a release number in it. I looked at the “Dayforce 2026.1.0 Upgrade – How to Prepare for Dayforce 2026.1.0” guide and it indicates that Dayforce will move to generic URLs in 2026.1, for example, for test the URL should be:
Test RESTful service request URL:
https://test.dayforcehcm.com/api/{namespace}/V1/{DayforceApi}
I’m wondering whether this URL change is the root cause of the failure? Is there a way to change the API base URL within Integration Studio after the upgrade?
