Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Error 153 on Youtube Videos

MeganCox
Tera Contributor

Everything has been working perfectly fine for months now. But this week, on all of the YouTube videos on our intranet pages, there's an error code 153. I haven't been able to find information on what the issue is. 

 

We used the Rich Content editor with the Video block and entered YouTube information on all the videos on topic pages. We have not changed any settings on our YouTube, and our IT department has let me know we have not made any updates to policies that would affect YouTube or ServiceNow. The only videos working are the ones that we have in the Video Carousel widget. I updated all of the videos the other day, and it randomly started working for an hour or so, but then it went back to having issues. 

Has anyone else experienced this? Any ideas for fixes that still allow us to have a video within the Rich Content widget?

MeganCox_0-1757691887213.png

 

39 REPLIES 39

Looks like they removed this PRB. Did you get a notice of what they merged it into?

I still see it as open

 

Screenshot 2025-11-07 at 6.27.30 AM.png

I don't see it either - just a record not found error. We are having the same issue so hopefully this gets resolved quickly.

Tessarollo
ServiceNow Employee
ServiceNow Employee

Hi Community,

 

As mentioned, ServiceNow is working on this behaviour through PRB1957001. To see this PRB, it must the attached to a case.

 

I just created an article to provide some details:

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2614673

 

We're investigating from the ServiceNow side. Thanks for your understanding and cooperation.

The knowledge article is visible, but the PRB seems to be hidden / has restricted access. The link above does not work for me, and if I manually search for the PRB number, I am not given any results. I would love to be able to track this, as it is negatively impacting many of our articles and content items.