Can't open Creator Studio, App Engine Studio, and ServiceNow Studio on PDI

[Kat Delegiewicz]

Dear Community,

I would appreciate any suggestion regarding the below issue.

I can't open any of these on my new PDI instance: Creator Studio, App Engine Studio, ServiceNow Studio.

Previous instance was failing to wake up so I requested a new one, actually a few of them since - none of the instances requested today was able to open any of listed "studios", although on the Developer Portal the respective plugins are shown as "installed".

I tried:

- Reset and wipe instance,

- Release instance, and request a new one instead,

- install each of available releases: requested Washington DC, Vancouver, Yokohama,

- used a different browser,

- even cleaned up cache and cookies, and repeated the above steps,

- tried to find the plugins responsible for each of the "studios" to repair them, but they were not even listed anywhere - either under System Definition > Plugins in the PDI itself, or under Activate plugin on Developer Site.

Now I gave up 😑

Please, could you suggest anything?

Thanks!!!

[BrianProvencher]

Check your permissions, sys properties, etc. 

• Ensure you have the "App Engine Studio Creator" role assigned to your user. 
• You may also need the "sn_app_eng_studio.user" role to see the App Engine Studio module in the navigator. 

• In the navigator, type "sys_properties.list" and press Enter.
• Search for the "glide.login.home" system property.
• Update its value to "home.do" and save the property.
• Log out and back in to see if the change takes effect. 

[Kat Delegiewicz]

Unfortunately, it didn't help 😞 I even wasn't able to perform all the steps because:

a) the roles you mentioned can not be found on the Roles' list,

b) I was already using System Administrator user, so it shouldn't be an issue in the first place,

c) with all my previous PDIs, regardless of the release (Washington DC, Xanadu, Yokohama), Creator Studio, App Engine Studio, and ServiceNow Studio were available instantly after the installation - no additional steps were ever needed.

It looks like issue with the instance(s) itself - please see the screenshots below, even the respective plugins are not available anywhere:

The pages are shown as "not found" while with my previous PDIs (before yesterday) it never happened:

_____________________

If it turns out to be a global issue with new PDIs, where should I report it? I guess it could have impacted multiple users as all PDIs requested by myself since yesterday have the same problem. I was trying to find any "help/support" place to raise a ticket regarding PDIs, but didn't succeed.

[Dr Atul G- LNG]

Hi @Kat Delegiewicz 

There are some issues with these modules. Either users are unable to open them, or if they can open the apps, they are unable to create custom apps. It's a known issue. Since there's no support for PDI, we can't do much to assist. You'll just need to wait and try again daily.

[Kat Delegiewicz]

Thank you, I tried the weirdest thing: released the PDI, waited for a few hours and requested new PDI (Yokohama release), but this time using an incognito browser window. Not sure if it was just a coincidence, but now the brand new PDI works perfectly 🙂