# Published integration instance not detected when updating existing OIN OIDC integration **URL:** \ **Category:** OIN Submissions\ **Created:** [April 17, 2026, 7:29pm UTC](https://devforum.okta.com/t/published-integration-instance-not-detected-when-updating-existing-oin-oidc-integration/35227 "2026-04-17T19:29:17Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![brett](https://avatars.discourse-cdn.com/v4/letter/b/bc79bd/32.png) [@brett](https://devforum.okta.com/u/brett)\ **Post date:** [April 17, 2026, 7:29pm UTC](https://devforum.okta.com/t/published-integration-instance-not-detected-when-updating-existing-oin-oidc-integration/35227/1 "2026-04-17T19:29:17Z")
Hi Okta team, We’re blocked trying to update an existing published OIN OIDC integration. In the OIN Wizard, when we try to edit the published integration, we repeatedly get: “Published integration instance not detected. To test for backward compatibility, you must have an instance for each supported protocol of your previously published integration in your org. Generate an instance of your published integration to create a new version.” Even after generating a new app instance, the wizard still does not recognize it as the published version and continues to show the same prompt. Relevant context: - app name: Software Analytics - org: integrator-9217138 - protocol: OIDC - the OIN team previously migrated this application to a new integrator org, and we suspect that may have broken the published-version mapping, but we have no way to fix it - we need to update our redirect URIs to include our new domain (antenna.dev) I found this Okta staff reply describing a manual fix for published version misalignment: > [@Missing Published version tester in APP](https://devforum.okta.com/t/missing-published-version-tester-in-app/31439/3): > > I am experiencing the exact same issue. The OIN app submission wizard is prompting me to install the currently published version of my app. I have: Created a new app via “Generate App” button on OIN Submission Wizard UI Installed app from App Marketplace Neither work. Also, the submission wizard is expecting the Published version of my app that is SAML-only however my currently published app version includes SAML and SCIM so I’m between a rock and a hard place. The suggested fix was: - create a new custom version based on the current default version - make that version the default - then add a new app instance without changes so the auto tester detects it as the published version However, it seems like those steps would need to be performed by someone on the OIN team. My questions: 1. Is this likely a published-version misalignment caused by the org migration? 2. Is there any self-service way to repair this in the admin/OIN UI? If not, can the OIN team apply the fix internally? 3. Is there any supported workaround for updating redirect URIs while this published-version detection issue is unresolved? We’ve already emailed [oin@okta.com](mailto:oin@okta.com), but I’m posting here in case anyone from Okta recognizes this failure mode or has guidance on the fastest path forward. Thanks, Brett ---
**Author:** ![andrew1](https://avatars.discourse-cdn.com/v4/letter/a/9de053/32.png) [@andrew1](https://devforum.okta.com/u/andrew1)\ **Post date:** [April 20, 2026, 1:34pm UTC](https://devforum.okta.com/t/published-integration-instance-not-detected-when-updating-existing-oin-oidc-integration/35227/2 "2026-04-20T13:34:57Z")
Hi @brett , Sending you a DM. Kind Regards, Andrew ---
**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\ **Post date:** [May 20, 2026, 1:35pm UTC](https://devforum.okta.com/t/published-integration-instance-not-detected-when-updating-existing-oin-oidc-integration/35227/3 "2026-05-20T13:35:12Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.