# Since recently builds are queued up for more than one hour

**URL:** <https://travis-ci.community/t/since-recently-builds-are-queued-up-for-more-than-one-hour/10530>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** travis-build\
**Created:** [November 10, 2020, 7:56pm UTC](https://travis-ci.community/t/since-recently-builds-are-queued-up-for-more-than-one-hour/10530 "2020-11-10T19:56:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nfx](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/nfx/32/5530_2.png) [@nfx](https://travis-ci.community/u/nfx)\
**Post date:** [November 10, 2020, 7:56pm UTC](https://travis-ci.community/t/since-recently-builds-are-queued-up-for-more-than-one-hour/10530/1 "2020-11-10T19:56:47Z")

</div>

Greetings,

Since approximately couple of weeks ago i’ve started noticing significant time spent in queue for PRs on our repository - [https://github.com/databrickslabs/terraform-provider-databricks/pull/407](https://github.com/databrickslabs/terraform-provider-databricks/pull/407) - is there anything that could be done to reduce delay timing back down to 5-10 minutes, as it was before?

Thanks,  
serge

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [November 11, 2020, 1:15am UTC](https://travis-ci.community/t/since-recently-builds-are-queued-up-for-more-than-one-hour/10530/2 "2020-11-11T01:15:37Z")

</div>

> [@Build delays for open source project](https://travis-ci.community/t/build-delays-for-open-source-project/10272/26):
>
> As was pointed out in [Builds hang in queued state - #6 by Montana](https://travis-ci.community/t/builds-hang-in-queued-state/10250/6) linked to earlier in this topic, Travis is moving workers from [travis-ci.org](http://travis-ci.org) to [travis-ci.com](http://travis-ci.com) in preparation to fully close .org (or rather, make it read-only) around the New Year. So you need to migrate to .com to stop experiencing delays. Note the caveats:
