Locked Out of Your PDI After Enabling AIUX? - Brazil Version

Gokul_SNOW
Tera Contributor

 

Recovering a Locked-Out PDI After Enabling the AI-Native User Experience (AIUX)

If you recently enabled the system properties aiux.experience or aiux.on_off_user_pref_enabled on your Personal Developer Instance (PDI) and found yourself completely locked out or facing a blank page, you are not alone.

Because the AIUX framework renders pages on entirely new infrastructure, a severe layout breakdown can hijack primary UI page routing, causing normal table endpoints to throw routing or frame-rendering errors.

If you are completely locked out, here is an advanced recovery method that may help you regain access without wiping your data.

1. Mobile UI Endpoint Bypass (Recommended)

The AIUX rendering engine primarily targets desktop workspace frameworks. In many cases, the legacy mobile web framework remains unaffected and allows access to update the problematic properties.

Steps

  1. Modify your PDI URL to point directly to the classic mobile interface:

    https://devXXXX.service-now.com/$m.do#/form/sys_properties/65a36c7f1b9807109ac055f0604bcbb5?sysparm_view=Mobile
  2. If the page loads successfully, use the simplified navigation menu to locate System Properties.

  3. Search for the property:

    aiux.experience
  4. Change its value to:

    false
  5. Save the record and refresh your instance.

This should restore access to the classic user interface and resolve the AIUX routing issue.


Thanks,
Gokul Subramaniam


💡 Tip: If the property above is not sufficient, also verify that aiux.on_off_user_pref_enabled is set to false, then clear your browser cache and reload the instance.

13 REPLIES 13

Note: Brazil Patch 1 does not fix this issue

JC Moller
Giga Sage

At this time there is no known solution for this issue or..? Any difference between a fresh Brazil instance vs upgraded one? 

 

- Christian

This Issue is currently happening when you enable the AIUX UI properties on both fresh and upgraded PDIs.

PDI upgraded from Australia to Brazil and now the AIUX is broken. With aiux.experience set to true, normal browsing fails and /aiux/builder/widgets says "Core scripts failed to load".

 

The console shows 404s for:

/sncapps/aix/assets/aiux-styles-loader.css
/sncapps/aix/assets/aiux-core-loader.js
/sncapps/aix/assets/core.js

 

Setting the property to false fixes it straight away, and true breaks it again. All three sn_aiux apps are on the latest versions, the aiux row in sys_service pings fine, and the logs and install trackers show nothing. My guess is the assets path is not served after the Brazil upgrade.

 

Has anyone got it working on Brazil, or found anything other than turning the property off?

 

- Christian