Bad Request (400) Error

[Gauri_Khole03]

Hello all,

When looking at individual UR in SOW you get a Bad Request (400) error. If you click Refresh it just comes back and if you close the error you're able to continue with your work.

Steps we follow

1] Navigate to Service Operations Workspace.

2] Open List and open record of Universal Request.

3] Go to any window.

4] Go back to 2nd step record

5] We will get Bad request error(400)

6] it's just stay for 2 to 3 seconds and just close automatically.

Could you please help me with this issue?

Thanks!

[Houston Vargas]

Yeah I got an answer. It’s a bug but it won’t be fixed until Washington release in Spring. It’s due to a Dynamic Translation plugin looking for content that it normally doesn’t have access to. That plugin is paid so it’s not like you can just fix it for free until Washington is out. Odd stuff to paywall a fix but anyway, it’s harmless just annoying more than anything. To be clear, it’s looking to dynamically translate URs to another language but most of probably don’t own the plugin so it’s essentially saying, the plugin is required and it can’t be found.

[AHE]

Hi Houston, thanks for your answer, this is not an acceptable answer of ServiceNow, this makes that an agent cannot work properly on an universal request on a workspace before Washington without the dynamic translations. I just received the same answer from ServiceNow, I'll push to see what they say.

[jpfasciana]

I'm having the same issue but have noticed that the error pops up only when the Universal Request does not have an attachment but the attachment sidebar pane is open.  If you close the Attachments sidebar pane and then reopen the Universal Request, the error does not pop up.