# Resolving Sync API Termination Issue in Label Studio

**URL:** <https://community.labelstud.io/t/resolving-sync-api-termination-issue-in-label-studio/195>\
**Category:** Label Studio Support\
**Tags:** api\
**Created:** [May 16, 2024, 5:21pm UTC](https://community.labelstud.io/t/resolving-sync-api-termination-issue-in-label-studio/195 "2024-05-16T17:21:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sajarin](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.labelstud.io/sajarin/32/56_2.png) [@sajarin](https://community.labelstud.io/u/sajarin)\
**Post date:** [May 16, 2024, 5:21pm UTC](https://community.labelstud.io/t/resolving-sync-api-termination-issue-in-label-studio/195/1 "2024-05-16T17:21:11Z")

</div>

#### Question:

> When trying to sync Source storage using the Label Studio UI, the Sync API gets terminated after about 3 minutes. Is there a time limit imposed on API execution in Label Studio?

#### Answer:

The timeout for the wsgi worker is known to be approximately 90 seconds, which can explain the early termination of the Sync API. Consequently, the platform does not support long-running background processes in the open-source edition.

Additionally, the use of `django_rq` for background tasks is an enterprise feature only.

However, to address this issue, you can attempt to use the `harakiri=0` setting for your wsgi workers to prevent them from timing out early by setting the `UWSGI_WORKER_HARAKIRI=0` environment variable.