
775cv (775cv) asked a question.
Hi there,
I'm getting 500 errors when accessing the Okta Workflows console. Unfortunately, logging out and back in didn't fix the issue and neither did clearing my browser cache. The thing that makes me think this isn't a browser issue is I'm getting the 500 error on the okta subdomain that was associated to my trial account. Now that I have a subscription, our subdomain changed but the workflows console didn't seem to get updated to the new subdomain.
If you could try and see if there's anything on the backend that needs to be updated to work with our new okta subdomain, I'd appreciate it.
Thanks,
Addison

@775cv (775cv)
Two things:
Ensure the user has Super Admin Role and is assigned to both (Okta Workflows & Okta Workflows Oauth) applicaitons.
If you are attempting to login through a custom domain this will not work. Make sure you are logging into the Okta domain (subdomain.okta.com) and not (customsubdomain.mydomain.com)
If you are still having issue after confirming the above this one is likely going to need an actual case created. There can be sometimes be issues when creating new tenants with the same name.
I've tried authenticating through the Okta domain and it doesn't work. The user I'm using is a Super Admin and is assigned to both applications.
The domain it ends up on when I launch the Workflows Console is trial-xxxxxxx.workflows.okta.com which was the domain of my trial account (i.e. my trial domain was trial-xxxxxxx.okta.com). Since becoming a subscriber, I have a new subdomain but this doesn't seem to be reflected on the Workflows side. I assume this is why the application is having issues as it is unable to verify my authentication for the trial domain.
Could you create a case for me or link me some documentation on how to do it myself? I'm new to the platform and this is the first thing I've needed support on. If there's somewhere better to put questions like this let me know.
Thanks!
@775cv (775cv) This is a great place to asked general usage questions in regards to Workflows. However, this issue is likely going to need customer specific information that shouldn't be shared publicly.
You are already logged in (otherwise you couldn't have posted to this forum). If you click your name (upper right corner) and chose My cases you should be able to dispatch a case.