Budget: 3500 UAH Deadline: 3 days
I will establish stable operation of the video upload script from diagnostics to final testing. I will check the OAuth tokens for expiration, YouTube Data API v3 quotas, and the queue logic between Google Drive and channels/playlists, as chaotic uploads are often related to the lack of retry logic in case of 403/429 errors or race conditions. Question: does the script run on a schedule via cron or is it triggered by the appearance of a file on Drive?
Budget: 8000 UAH Deadline: 5 days
Hello. I have been working with Python for over 9+ years. I am ready to fix the script's work.
Budget: 5000 UAH Deadline: 30 days
I will turn your automation into iron logic: through Cursor, I will analyze all execution paths of the code to find where exactly the identifiers are "lost" and duplicates occur. The budget and deadlines are in personal correspondence.
Since the system is currently working chaotically, do you have a local database for recording statuses, or is the script blindly relying on Google Sheets, which simply cannot keep up with the speed of the code?
Budget: 2000 UAH Deadline: 2 days
I can take on the correction and stabilization of this script.
I am ready to start immediately after gaining access to the code and the current logic of operation.
Budget: 4000 UAH Deadline: 4 days
Hello, Anastasia. I have thoroughly analyzed the list of bugs in your automation. The problem with your current code is not in the logic, but in the lack of transactionality and error handling. The script is written linearly: if the connection to Google Sheets drops after successfully uploading a video to YouTube, the script crashes, data is lost, and duplicates are created on the next run.
I propose an architectural refactoring of your code (acting as a Senior Backend Engineer):
1. Implementation of transactionality (State Machine):
I will rewrite the logic so that the script records each of its steps. We will add intermediate state saving (in local JSON/SQLite on the TimeWeb server or directly in the "Status" column of your table). If the script crashes, upon restart it will clearly continue from the point of failure (for example, it will simply add the link to the table), rather than re-uploading the video.
2. Isolation of channels (routing):
The problem with channel confusion arises due to a conflict of OAuth2 tokens. I will implement strict credential management, where an isolated session will be created for each YouTube channel. This will prevent videos from being uploaded to the wrong channel.
3. Exponential Backoff and Timeouts:
The script "hangs" because network requests do not have a timeout. I will set strict timeouts for all requests to Google Drive/YouTube API and add a pattern for automatic retries (using the tenacity library). In the case of 403 or 429 errors from Google, the script will algorithmically wait and retry the request, rather than "freezing."
I work exclusively through Safe for your and my security. I am ready to start auditing your code (via Git or archive) today.
Budget: 3000 UAH Deadline: 3 days
Hello, Anastasia!
All 4 problems are symptoms of one root: there is no state machine. The script does not maintain the atomic status "taken for work → executed → updated," hence the chaos, duplicates on different channels, and hangs on the same IDs.
What I am doing:
status field in Sheets: NEW / IN_PROGRESS / DONE / FAILED
lock file on Time4VPS (two cron processes do not run in parallel)
idempotency: one file_id → one processing row
retry with exponential backoff on 429/403 from YouTube API
deterministic mapping "identifier → channel"
I am new to Freelancehunt, but I write Python + Google API in production daily (StratBase.ai). Lower rate for the sake of the first feedback here.
3 days, 3,000 UAH. Question: cron schedule or trigger on the file in Drive?
Budget: 4000 UAH Deadline: 3 days
Good day. I worked on a similar project, downloading videos from TikTok and publishing them on various YouTube channels with logging.
Budget: 4000 UAH Deadline: 3 days
Good day, I can confirm my ability to complete the task of fixing bugs in Python automation for uploading videos to YouTube. To start the work, I will analyze the existing code and identify the sources of the problems, and then I will apply my knowledge of the youtube-api-python library to fix the bugs and ensure reliable video uploads. For the implementation of this project, I will need additional information about the specifics of the bugs and the requirements for completing the work.
Budget: 7000 UAH Deadline: 3 days
Hello! I am Nina, the manager of developer engineer Valentin.
We have reviewed the issues with your automation. Chaotic loading and duplication are a result of a lack of state control and improper handling of API limits. Valentin specializes in creating fault-tolerant Python systems, and we offer not just "bug hunting," but an architectural solution to the problems.
What Valentin will provide:
Process isolation: Implementation of a locking system so that the script does not launch duplicate processes on Time4VPS.
Transactional logging: Redesign of the connection with Google Sheets. Each ID will be recorded in the table before and after successful loading, which will eliminate data loss.
Retry logic (Exponential Backoff): The system will intelligently respond to 403/429 errors from YouTube without interrupting the overall queue.
Clear mapping: We will restore and document the logic "ID → Channel" to eliminate chaos in video distribution.
Timeline: 2–4 days (including monitoring the first launches).
Budget: 6,000 — 8,000 UAH (for quality refactoring with a stability guarantee).
Could you let us know if you have error logs from the server for the past few days? This will allow Valentin to instantly localize the "bottleneck" in the current code.
Best regards, Nina.
Budget: 5500 UAH Deadline: 4 days
Hello.
I have reviewed the description of the problems. I can get involved in fixing your Python automation and bring the loading logic to a stable and predictable state.
From what I see, the issue here is not just one error, but several related nodes: unstable loading, loss of connection between the file and publication, duplication of identifiers, incorrect distribution between channels, and stopping the processing of individual records. Such tasks need to be not just "tweaked," but properly examined in terms of processing logic, queue, state preservation, and connections between services.
I can do:
— find and fix the causes of unstable loading
— sort out logging and preservation of identifiers
— eliminate duplication and distribution errors between channels
— restore correct processing logic for new records
— check the operation of the Google Drive API, YouTube API, and Google Sheets integration
— bring the script to a more stable working state
I work on such tasks as a technical analysis of the system, not as a point fix, so it is important to bring the process to normal predictable operation.
I am ready to promptly engage in the task.
Budget: 3500 UAH Deadline: 2 days
Good day, I understand your problem and am ready to solve it in the shortest possible time.
Budget: 6000 UAH Deadline: 2 days
Good day
I can take on this task as I have experience with YouTube API, Google Drive API, and automation in Python
Regarding the described issues, I see clear reasons: there is no reliable system for tracking processed files, the logic for binding channel identifiers is not atomic, and most likely there is no retry mechanism for API failures
Budget: 25000 UAH Deadline: 14 days
Hello!
I understand that it is necessary to fix the existing Python automation for uploading videos to YouTube, which is working unstably and has lost its expected logic of operation.
I will do this using n8n.
Budget: 5500 UAH Deadline: 4 days
Good day! I have experience in developing similar scripts, could you tell me if the system started working unstably from a certain moment, or if it was not working well from the very beginning?
I am ready to complete it in 3-4 days.
Budget: 5000 UAH Deadline: 2 days
Hello :)
I have over 10 years of experience in Python development, having implemented a huge number of similar automations.
Feel free to write, I would be happy to learn more about your current solution and discuss your task.
Budget: 6996 UAH Deadline: 3 days
Hello! We are a small team that has been engaged in web development and process automation through Google Drive and YouTube API for over 4 years, and we are ready to stabilize your software "turnkey." We implement a quality system for checking existing videos to prevent duplication, set up a reliable verification cycle for new files on the disk, and ensure the correct recording of all IDs in Google Sheets. Our experience of over 4 years allows us to guarantee the stable operation of the system even with large volumes of data; be sure to check our work examples that demonstrate high technical culture: freshagro.com.ua, farfieworldwide.com, rivnekolo.com.
Budget: 8000 UAH Deadline: 4 days
Good day! My colleague and I have been professionally engaged in technical design and development of server solutions for media content automation for over 4 years, so we will help you eliminate chaos in the work of the uploader. We will implement a frontend audit of logging in your table, rewrite the mechanism for tracking processing statuses, and establish a clear binding of files to specific playlists and channels. We will ensure the technical perfection of the script execution on your Time4VPS server by setting up an error logging system for immediate response to the stoppage of processing identifiers; our experience is confirmed by successful projects in automation: drkukharevich.rivne.ua, crave-agency.com.ua, jk-solution.com.ua.
Budget: 14000 UAH Deadline: 7 days
Hello! My partner (designer + full-stack) and I have been specializing for over 4 years in the development of complex automation systems in Python and deep integration with Google API, so we will professionally conduct a technical audit and refactoring of your script. We will design the database architecture in Figma to visualize new connections "identifier → channel," ensuring technically flawless logic for loading queues and excluding duplicates through uniqueness checks in Google Sheets. Our experience of over 4 years allows us to stabilize operations on Time4VPS by setting up correct handling of tokens and YouTube API limits for uninterrupted video publishing; take a look at our work in terms of technical accuracy and automation: hyperfi.tech, espressolab.com.ua, hudi.com.ua.
Budget: 2000 UAH Deadline: 1 day
Hello.
First, I will reproduce the failure in your Python environment and localize the point of failure in the loading chain: data source, authorization, response format, save path, or dependencies after the update. After that, I will make a pinpoint fix, run the scenario again, and check to ensure that the error does not return on the same input.
Before starting work, I need to clarify:
- access to the code or repository
- error log or step after which the failure occurs
- which specific source/module is being used for loading
- whether there is a staging or test copy
I can start right away.
Budget: 9000 UAH Deadline: 10 days
Hello! I am the founder of the engineering agency Vaysed. What you are describing is a classic disease of automation scripts that have grown from a simple MVP but lack built-in fault-tolerant architecture.
Chaotic loads, duplicates, and processing stops occur due to three main reasons: lack of state management, ignoring YouTube API quotas, and conflicts of parallel executions (when cron on Time4VPS starts a new process while the old one has not yet finished downloading a heavy video).
We specialize in building reliable data pipelines and will solve your problem not with crutches, but with proper engineering refactoring:
Implementation of State Machine (Finite Automaton): We will tidy up your Google Sheet (or deploy a lightweight local database on Time4VPS). Each video will receive a strict status (NEW, DOWNLOADING, UPLOADING, SUCCESS, FAILED). The script will only take files with the status NEW into work and will immediately block them for other processes. This will 100% eliminate duplication across different channels.
Transactionality and Failure Protection: If the connection drops during the upload to YouTube or the API returns an error (which happens often), the system will not "forget" about the video and will not stop processing this identifier forever. It will correctly log the error and queue the file for a retry (Exponential Backoff).
Strict Routing: We will rewrite the logic of mapping "identifier → channel/playlist" so that the system deterministically understands exactly where a specific file should go and will necessarily record the received YouTube ID back into the table.
We are creating an enterprise-level architecture that works reliably and predictably 24/7. You can evaluate our engineering approach to developing integrations and microservices in our portfolio: https://vaysed.me/
I am ready to connect to your server on Time4VPS, conduct an audit of the current Python code, and create a clear plan for its stabilization with a timeline. Write to me to discuss the details!
Budget: 5000 UAH Deadline: 1 day
Hello! I can implement it. Write to me privately to discuss all the details. I will be glad to cooperate!
Budget: 1000 UAH Deadline: 2 days
Hello, I am interested in your offer. I already have ready-made script options similar to the one you need. If necessary, I can completely rewrite it for you. The deadline is 1-2 days.
Budget: 10000 UAH Deadline: 1 day
✋ Hello! We are the IT company dZENcode.
We can help with fixing Python automation and restore stable loading logic.
Where is the logic for binding the identifier to the channel currently stored?
Is there access to the code and the Google Sheets table?
You can find detailed information about our services and rates on our website: 
Freelancehunt
Take a look – we will discuss the details of the work further, write when you are ready.
The final cost is determined only after clarifying the scope and requirements.
___________________
Best regards,
Manager of dZENcode
Our strengths:
💎 10+ years providing IT services: Outsourcing, Outstaffing
🔥 90+ in-house specialists
🚀 Projects "from scratch" and for support
⚙️ SLA and post-production support
✅ Contract with the company, guaranteed results!
🔥 250+ public reviews since 2015.
Budget: 3500 UAH Deadline: 3 days
Hello! I am a Python developer specializing in integrating various APIs and automating processes. I often encounter similar bugs in script architecture, so I understand how to restore stability to the system.
I suggest discussing the details in private. If you provide access to the repository, I will review the code, find the cause of the chaos with the identifiers, and then I will give you a precise timeline and cost.
Write to me, I am ready to look at the project!
Budget: 4000 UAH Deadline: 2 days
Hello, I am ready to take on your project and fix the error when uploading the video, I have extensive experience in automation, feel free to contact me.
Budget: 5000 UAH Deadline: 2 days
Good day! I have familiarized myself with the task and am ready to start.
Experience:
• 4 years in Frontend and Backend development
• 2 years of commercial experience in product and blockchain
• Working with production code and real financial scenarios, as well as automation and Python
Some of my projects:
https://contentbuilder.ai/ - a commercial project from the USA, where I worked as a full-stack developer and implemented most of the functionality
https://freelancehunt.com/showcase/work/procasino/2025898.html
https://freelancehunt.com/showcase/work/bionrgg/2025897.html
Budget: 1800 UAH Deadline: 1 day
The description is very similar to a typical problem of "desynchronization" of logic + states in systems with Google API. What you are currently experiencing (chaotic uploads, duplicates, loss of identifiers) is usually a result of poorly constructed tracking of processing and lack of a clear queue/status.
I have experience with:
• Python automation
• YouTube API / Google Drive API
• Google Sheets as a logging system
• server tasks (cron, long-running processes, VPS)
What I will do:
• analyze the current logic of the script and find the "breakpoint"
• restore stable communication: file → identifier → channel → status
• eliminate duplication and establish a clear binding to channels
• implement proper logging (so you can see what is happening in the system)
• ensure predictable and stable operation (queue / statuses / retries)
I work not with "patches," but I bring the system to stable logic so that it does not break again in a week.
I can connect immediately and start diagnostics.
Budget: 16300 UAH Deadline: 2 days
I will fix issues in the Python script for automating video uploads to YouTube. I will analyze upload instability, problems with identifiers, and duplication between channels. I will implement logic for clear interaction between files, identifiers, and channels, as well as establish stable logging in Google Sheets. I am ready to complete the task and make corrections.
Portfolio - Freelancehunt
Budget: 4000 UAH Deadline: 4 days
I have experience in developing and stabilizing automations in Python with integrations through API. I am ready to fix the logic of your script if you provide access to the code - according to your requirements and with quick feedback. Write to me!
Budget: 3000 UAH Deadline: 3 days
Good day, I have worked with all the specified APIs, I administer servers. I will look at your code, I will try to fix the problems. Was it written a long time ago? There are constantly some changes in the API, most likely because of that it does not work.
Budget: 5000 UAH Deadline: 4 days
Good day.
I can take on the stabilization and refinement of your automation in Python that uploads videos from Google Drive to YouTube.
What I see regarding the task: it is necessary not just to "fix the upload," but to restore the expected logic of the entire processing: — stable scenario for file appearance → verification → upload → logging; — correction of work with identifiers; — elimination of duplicates; — fixed binding "identifier → channel / playlist"; — correct reprocessing of new videos for the same identifier; — checking the logic of logging in Google Sheets; — analysis and correction of work on the Time4VPS server.
Budget: 4000 UAH Deadline: 5 days
Hello, I would be happy to take on your script! I have extensive experience in development with Python, including working with third-party APIs. Right now, without the code and access to the deployment environment, it is hard to say what exactly is going wrong. If the script worked correctly before, there may be a problem on the server (memory clogging, miners). If it has always been like this, then the script was poorly written from the very beginning. I will help figure everything out and make the script's operation stable.
Budget: 8000 UAH Deadline: 30 days
Has knowledge of Python and writing projects from scratch can take a look.
Budget: 10000 UAH Deadline: 4 days
Good day.
I have reviewed the description of the problems. Here, most likely, the issue is not just a separate bug, but that the logic of the pipeline itself has been disrupted: the file appears, but the system does not consistently pass through all stages of processing. That is why you currently have chaotic uploads, duplications, omissions, and a lack of proper control over identifiers.
I can engage in the task not just as a performer to "fix the script," but as a person who will restore the expected logic of the entire automation.
What I will do in the work:
- I will check the current Python script and the actual processing scenario
- I will find where exactly the logic is lost between Google Drive, Google Sheets, and YouTube
- I will restore normal logging of identifiers
- I will eliminate duplication between channels
- I will fix the correct binding of "identifier → channel / playlist"
- I will check why some videos do not reach the upload stage
- I will correct the script so that new videos with the same identifier are also processed correctly
- I will stabilize the operation on the Time4VPS server
- After the corrections, I will test the entire chain on real cases
For me, the key here is not just to achieve a one-time upload, but to return control and understandable logic to the system so that you can see:
what has been processed,
what is in progress,
what has failed,
and why exactly.
Regarding the timeline:
- Audit and localization of the cause: 1 working day
- Correction and stabilization: 2–4 working days
Regarding the cost:
- 350 USD for audit, correction, and testing
- If during the process it turns out that part of the logic needs to be rewritten more deeply, I will inform you of this before starting additional work
I am ready to get involved promptly. If you provide access to the server, script, spreadsheets, and API configuration, I will be able to quickly give a clear picture of where exactly the system is breaking and how to fix it properly.
Budget: 2000 UAH Deadline: 1 day
Good day.
I am ready to join your project and stabilize the current Python script for uploading videos from Google Drive to YouTube.
Budget: 5700 UAH Deadline: 5 days
Anastasia, I see here not just bugs, but a failure in the logic of the entire automation. I would start with restoring a stable chain: new file in Drive → correct ID entry in Sheets → clear assignment of channel/playlist → publication on YouTube without duplicates. I will also check why part of the IDs stopped logging and why the processing stops after the first run.
I work with Python automation, APIs, and scripts on the server, so I love tasks like these, where I need to not just "tweak" but find the cause of the chaos and make the system predictable. If you give me access to the code and logs, I will quickly localize the problem and propose a stable solution.
Budget: 3000 UAH Deadline: 2 days
Good day, I have 2 years of commercial experience with Python, I can fix your problem.
Budget: 3500 UAH Deadline: 10 days
Good day!
I can restore the expected logic of your pipeline Google Drive → YouTube (multiple channels/playlists) with logging in Google Sheets on Time4VPS.
What I will do regarding the core issues:
Instability / “chaos” of uploads: I will analyze the end-to-end flow (cron/systemd, logs, YouTube API quotas, Drive errors), introduce a clear state machine: detected → in queue → uploading → published / error with retries and backoff (considering API limits).
Identifiers in the table: I will restore the canonical source of truth (Sheets + local SQLite/JSON lockfile on the server to avoid race conditions), normal append/update of rows, idempotency check (one file/one fileId → one processing row).
Duplication and mixing of channels: I will establish a strict mapping folderId/fileId/rule → channel_id/playlist_id, prohibit “reassignment” without an explicit rule, protect against double execution (file lock / singleton worker).
“Processed once and done”: usually this is a cache/marker “already done” without versioning or date filtering — I will implement incremental processing (change modifiedTime, new files in the same folder, a separate log for processed_revisions).
Technically: Python, OAuth/service accounts according to YouTube/Drive API restrictions, structured logs, .env for secrets, systemd timer/cron with parallelism control.
In work, I use Cursor for speed; I keep the state architecture, quotas, and integration correctness under control.
Stages: code + logs audit (1–2 days) → fix data model/table → stabilize the worker → test on 10–20 files → hand over instructions.
