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

Hello has anyone seen a case where an existing integration that ran fine in the past will not run.

  • September 15, 2026
  • 4 replies
  • 3 views

Originally posted by Jeff Dooley on May 21, 2026 at 10:14 AM.

 

Hello has anyone seen a case where an existing integration that ran fine in the past will not run. If I click "Run" or "Save and Run" it fails immediately with this error :

 

There is nothing in the logs, it just seems to not be able to run. The integration ran fine in the past, the site was recently upgraded to Release 2026.1.1.1 Build: 73.0.10.13915 Build Definition: DayforceGlobal-r73-CI. If ran fine before that. I tried to create a new integration as a test but it fatally fails with the same error when I try to select a data source. My user role looks OK and it has the permissions for Integration Studio.

    4 replies

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Barbara Buchanan on May 22, 2026, 9:31 AM.

     

    Hi @Jeff Dooley​ , I have experienced this with most upgrades and had to close out and come back to it later. After (hour(s)? days?) it seemed to have resolved itself.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Jeff Dooley on May 22, 2026, 10:20 AM.

     

    Thank you @Barbara Buchanan​  that is good to know, I will try again, hopefully it will correct itself soon.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Sage Konstanzer on Jun 3, 2026, 4:04 PM.

     

    I had this problem for a while on benefits exports and it ended up being that an earning grouping was missing an XRefCode.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Jeff Dooley on Jun 9, 2026, 7:48 AM.

     

    Thank you @Sage Konstanzer​! I reviewed the earnings groupings and one was added without the xref code, that was the issue.