Hi Team, we have a requirement to test few modules in the website which is still in development mode. here we have a issue that URL’s are getting unpublished and suddenly URL is getting 404 error. Can anyone suggest how can i handle unstable url’s like config or orchestrator asset. We have more 60 usecases and each Test case involves in 4 different environments, using asset is not good option i think. Can you please help me here
Hi @Madhups
Store all environment-specific URLs in a single Config file and read them at runtime in each workflow. Use an input argument or parameter to select the active environment, and wrap navigation steps in a Try-Catch to handle 404 errors so tests continue. Log any failed URLs for easier debugging, avoiding reliance on Orchestrator assets.
Happy Automation
hi @Madhups
my suggestion to handle unstable URLs, the simplest approach is to avoidd hardcoding anythin in your test cases. Use a single asset per environment that stores only the base domain, and build the rest of the path inside each test. This way, when the dev team changes or unpublishes a URL, you only update the asset once and all 60 test cases keep workin
If a module temporarily returns 404, you can add a quick check before navigation and try an alternative path if one exists, keepps everything centralized and easy to maintain
If this helped, please mark it as the solution so others can benefit too 
To handle unstable URLs, avoid hardcoding them in test cases.
Instead, store only the base domain in a single asset per environment and build the rest of the path dynamically in each test.
This way, if the URL changes, you update it only once instead of in every script. If a page returns 404, add a quick check and switch to an alternative path. This keeps maintenance easy and centralized.
you can place in config and store the config in storage bucket in orchestrator so that any change can happen in file and no need to change the package
cheers