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
hlias kantzos
19,191 Pointsproblem with 2 code challenges:
problem with 2 code challenges:* * *
Building the Friendship UI: Code Challenge: Finding and Building Models * * *[http://teamtreehouse.com/library/programming/building-social-features-in-ruby-on-rails/building-the-friendship-ui/finding-and-building-models]
Using AJAX: Code Challenge: Controller Formats * * [http://teamtreehouse.com/library/programming/building-social-features-in-ruby-on-rails/using-ajax/controller-formats] * *
I can not submit any code.* * *
returns "there was a problem connecting to the code challenge engine". has anyone the same problem?* * *
Thanks!
3 Answers
Jesus Valdivia
7,647 PointsI had the same problem a couple of times. I just wait 10 or 15 minutes and then try again and works fine.
J.T. Gralka
20,126 PointsYeah. Sometimes there are some issues submitting the code challenges. Often times, if I get that error, I end up retrying and reclicking over and over and over again until it submits, and if for some reason it doesn't, then I just wait a few minutes. If you find that you are getting this error message frequently, don't hesitate to email the Treehouse support team at support@teamtreehouse.com. They're normally very prompt and friendly, and if there is a technical issue on Treehouse's end, they forward the ticket to the appropriate teacher or dev team member so that the problem gets fixed!
Brandon Barrette
20,485 PointsI e-mailed over the weekend and they said it's a "known issue" they are working on and to try again the beginning of this week (July 1).