Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Thomas Moore](https://uploads.teamtreehouse.com/production/profile-photos/8858562/micro_TomM.jpg)
Thomas Moore
Front End Web Development Techdegree Graduate 25,371 PointsHelp! I can't move forward as the code challenge keeps hanging!
Hi there,
There appears to be a bug with the coding challenges in this course.
Customising Django Templates – Part 2: Building Custom Tags – Step 6: Create an Inclusion Tag (Coding Challenge)
When I enter the code on this challenge and press "Check work" the browser hangs and then I get this error message "Oh no! We didn't hear from the challenge service in a timely fashion." (attached below).
It's very frustrating as I know how to complete the coding challenge, but am prevented from signing off that course.
Could it be my browser? Do you recommend a particular browser setup to complete these challenges?
Thanks, Tom
1 Answer
![Steven Parker](https://uploads.teamtreehouse.com/production/profile-photos/969492/micro_tool_chess_set_2.jpg)
Steven Parker
230,688 PointsYour attachment doesn't seem to be present, but just in general, when the system does not "hear from the challenge service in a timely fashion", it is likely that the code contains a loop that never ends. Look for typos in conditions or other reasons a test condition might never change state, or unintended recursion (a function or method calling itself).
If that hint doesn't help you find it, show your code (preferably with a snapshot link) and provide a link to the challenge page to make it possible to replicate the issue.