# Knowledge Base ## Reverse Connectors ### Sync getting stuck in QUEUED status for a particular sync in STAGING If it's getting stuck in QUEUED status, it can mean 2 things: - The workers are not picking it up. In this case, check the **dc_rvrs.service** logs. - The run is getting error out even before registering the RUNNING status. In this case, there will be no sync specific log file. So check the preinit logs like this: ```tail -100f /user_home/dc_frontendtest_004/.preinit_logs/preinit.log ``` ## Forward Connectors ### Pipeline run in RUNNING status for a long time First check it's log file and see whether it is still running or not (By monitoring the log file for some time). If it is running, then there is nothing to be done since it's the accepted scenario. If not, then open all the worker machines. In STAGING, it would be **worker-stage-0.datachannel.co, worker-stage-1.datachannel.co etc.** In PROD, it would be **worker-0.datachannel.co, worker-1.datachannel.co etc.**. In all the workers run this command, ```bash= ps -ef|grep {configured_pipeline_id} ``` If the process is still running then it will show in one of the machines. You can either kill it if you are sure that something has gone wrong or wait if you are not sure. ### {account_workspace_path}/{datasource}/{pipeline}/run.lock PERMISSION_DENIED in run logs. Check the permissions for this directory using `ls -ltr`. The directory should belong to the user. This happens sometimes (reasons still unknown.. something to do with middleware). If the folder is owned by `root`, simply do a `sudo chown -R {client_user}:{client_user }{directory}` ## Transformations ## DBT ## Warehouses ### Warehouse row is added in data_warehouse table, but columns like `db_conn_schema` are not populated correctly (dummy values) This means that something went wrong during the middleware call for data_warehouse. Check the middleware logs.