Need to fix a bug in the current version of the bot.

Budget: 15000 UAH Deadline: 3 days

Good evening, Sergey!

I am ready to connect to the current bot on aiogram 3 and specifically fix the operation of the "nor" cleaner, without affecting the existing chat logic.

First, I will localize the cause of the failure: I will check the scheduler, time zone, cleaning conditions after 7 days, statuses in MySQL, queue and TTL in Redis, retries, possible races, and error handling.

After diagnostics:

— I will reproduce the problem on a test copy;
— I will make an isolated fix;
— I will check the scenarios of active chat, completed transaction, closed chat, and absence of messages for more than 7 days;
— I will set up clear logs for the cleaner;
— I will make a backup before deployment;
— I will check the operation of the fix on the server.

I will not rewrite the working system unnecessarily. The goal is to eliminate a specific bug and not pull other parts of the project along with it.

To start, I need the repository, access to the logs, and information on how the cleaner is currently launched: cron, separate async process, or another scheduler.

Deadline — up to 3 working days.
Cost — 15,000 UAH.
Work through Safe. Expand

Budget: 700 UAH Deadline: 3 days

Good evening! I am ready to take on this bug. aiogram v3 + aiohttp + MySQL/Redis is our daily stack, and dealing with someone else's code is something we do constantly.

In essence: the cleaner is not working on schedule. In such cases, the reason is usually one of three. The scheduler lives inside the worker and restarts with it; the TTL of the last activity is overwritten with the wrong key in Redis; or the time of the last message is stored in MySQL in a different timezone than the one used to count the 7 days. First, I will take a log of one complete cycle of the cleaner and compare it with real records from several burrows to see where the discrepancy lies.

I work selectively: I only adjust the logic of the scheduler and the return of the burrow to the queue, I do not touch the chat mechanics and the rest. Before deploying to production, I show the diff and run it on a copy of the database to ensure the fix does not lead to other problems.

The price is 700 UAH, the deadline is 2-3 days from the moment of access to the server and repository. I am taking it at the starting price because I am gathering my first reviews on Freelancehunt.

A question regarding the matter: is the cleaner launched as a separate asyncio task inside the bot, like APScheduler or as a system cron? And where is the time of the last activity stored in the burrow, in MySQL or in Redis with TTL? This determines whether it is a one-hour fix or if the scheduler needs to be moved to a separate process.

There are live bots in operation, I can show them in the chat.

Petro Pankov, BotCraft Group Expand

Budget: 12000 UAH Deadline: 3 days

The deadline is approximately 3 working days for diagnostics, fixing the cleaner of the queues, checking scenarios, and careful deployment on the server. The budget is 12,000 UAH, if the problem is indeed in the schedule, queue, or cleaning conditions, and not in a deeper malfunction of the chat model.

There is a nuance here - I would not touch the chat work more broadly than necessary. The logic is this - I check the launch of the cleaner, the state of the queue in MySQL or Redis, the conditions of 7 days without messages, deal statuses, then I make minimal adjustments and run scenarios with an active deal, a closed chat, an empty chat, and returning the queue to the queue.

I need access to the server, repository, or project folder, environment settings through a secure mechanism of the exchange, and an example of 1-2 queues where the cleaning did not work correctly. Code and server commands are not to be taken outside the task.

I will clarify 2 points to avoid misjudging the assessment:
> the cleaner is currently launched via cron, a separate asyncio process, an aiohttp task, or within the main bot
> the queue of queues is stored in MySQL, Redis, or in a mixed scheme

Similar works of ours:
> https://business.ingello.com/platforma - a platform with roles, business logic, and process management
> https://business.ingello.com/forma-bpm - automation of queues, statuses, and internal processes
> https://systems-fl.ingello.com - the main profile of Ingello Systems for FLH

If after diagnostics it turns out that the problem is not just one bug, but in the architecture of cleaning and queues, I will separately propose a short design phase. Better to measure seven times than to fix each new queue manually later =) Expand

Budget: 700 UAH Deadline: 2 days

Sergiy, good afternoon. It is important to correct the conditions of the cleaner without affecting anonymity and parallel chats. I will start with the reproducible failure scenario and the transition map: closed chat, no agreement, 7 days of inactivity, removal of participants, and returning the burrow to the queue. I am working with Python asyncio, aiogram 3, MySQL, and Redis; I will make precise edits and check them under edge cases.

Budget: 4000 UAH Deadline: 7 days

Hello, I created a similar Telegram service on aiogram v3 for interaction between clients and performers: profiles with roles (RBAC), paired chats between parties, a queue of dialogues, automatic cleaning of inactive chats based on a timer in Redis. Analyzing someone else's code directly on the server with aiohttp webhooks and MySQL was also part of that work.

If the cleaner is not running on schedule, the most common reason is that the timers live in the process memory and reset upon restart, so it’s worth moving the 7-day countdown to TTL in Redis or a separate scheduler, which eliminates floating triggers.

Could you tell me if the cleaner runs as a separate asyncio task or through an external scheduler, and how many nooks are currently in the queue? And where is the last activity in the chat recorded, in MySQL or Redis?

I suggest we connect, and I’ll also sketch out the logic scheme for the cleaner tailored to your paired nooks, so that the fix doesn’t lead to other problems.

Budget: 1200 UAH Deadline: 2 days

I work with aiogram v3 + asyncio/aiohttp, MySQL, and Redis - I can understand someone else's code without rewriting it. From the description, it seems that the cleaner Nor does not maintain the schedule due to a task tied to the webhook's lifecycle and does not survive a restart, or due to the TTL of keys in Redis, which are overwritten upon re-recording. I will check the scheduler and logs directly on the server, reproduce the case, show the reason before making corrections, then I will fix it and leave a test for the cleaning schedule. Before any changes, I make a backup of the code and the database. Please tell me - is the bot on webhooks via aiohttp and what is currently responsible for the schedule - APScheduler or a custom loop?

Budget: 1000 UAH Deadline: 1 day

Hello. My name is Volodymyr, I am a Python and Node.js developer, as well as the founder of the engineering agency Vaysed. I have thoroughly reviewed your task regarding fixing a bug in the existing Telegram bot on aiogram 3. I understand that it is necessary to fix the proxy chat cleaner algorithm, which is scheduled to correctly free inactive paired chats without harming the rest of the bot's functionality.

The problem with the cleaning schedule is often due to incorrect use of asyncio, blocking the event loop by other bot processes, or the lack of a reliable scheduler that would maintain state in Redis. Since you are already using Redis, I suggest conducting a quick audit of the current cleaner script directly on your server. I will find the cause of the timer failures and optimize this module by checking the logic of matching timestamps of the last activity and the status of transactions with MySQL. This will ensure that chats inactive for more than 7 days will be consistently cleaned and returned to the queue, while current dialogues will not be affected. All changes will be made precisely and safely.

I have extensive experience in developing complex bots on aiogram 3, working with webhooks, and managing asynchronous queues. For example, during the development of the Lumos system, I implemented uninterrupted processes that operate on strict schedules 24/7 without any failures. Also, in the PAYBACK CARTEL project, I built a reliable architecture for routing and session management.

You can view my portfolio at this link: Freelancehunt

I suggest moving to private messages to discuss access to the server and review the logs of your cleaner's operation.

Budget: 1500 UAH Deadline: 1 day

Good evening. I am engaged in the development and configuration of Telegram bots. I can help solve your problem, quickly conduct diagnostics, and fix the issue. I am ready to discuss the details and start working, feel free to write.

Budget: 1111 UAH Deadline: 11 days

Good day, I have a lot of experience in this, but without seeing the code, it's hard to say anything. It would be very desirable to look at the code, then it will be possible to say something more specific.

Budget: 2000 UAH Deadline: 2 days

Hello. I have worked with everything listed.
I can take it on.
We will decide on the price depending on how much needs to be corrected.
In general, if anything, let's discuss it in detail, you can show me where it doesn't work, and I will take a look at the code.

Budget: 1500 UAH Deadline: 2 days

Hello. The main challenge of this task is to stabilize the operation of the background "cleaner" of anonymous chats ("Nir") without breaking the existing message routing in aiogram v3. The fact that the cleaner disrupts the schedule usually indicates a blockage of the asyncio event loop, incorrect operation of the current task scheduler, or hanging transactions when checking the status of deals and 7-day inactivity. I will localize the bug directly on the server: optimizing MySQL queries for accurate tracking of the last message time and setting up a reliable mechanism for resetting empty chats back into the queue through the existing Redis. I will do all this precisely, preserving the current logic of isolation (paired chats) for clients and performers unchanged. I have extensive experience working with complex Telegram architectures on aiogram v3.

Budget: 1250 UAH Deadline: 2 days

Hello! I understood the problem with the chats (norms): they are not cleared on schedule and do not return to the queue. I have experience in developing Telegram bots using asynchronous Python with webhooks, MySQL, and Redis. I have definitely worked with the logic of auto-clearing chats based on timers and re-queuing.

In what format do you store the timestamp of the last message in the chat?

Budget: 700 UAH Deadline: 2 days

Sergiy, the key risk here is that the "cleaner" of the nests affects the state of deals in Redis and the connections of users in MySQL. If the lag is simply adjusted, it can silently break the queue: the nest will return to circulation, while there is still an active deal.

Approach to the fix:
— first, I will trace the current algorithm of the cleaner: what exactly triggers the cleaning (cron, event loop) and what conditions it checks before deletion
— I will restore the logic of "7 days without messages OR chat closed AND no active deal" — so that the nest returns to the queue only under the correct condition
— I will check how the Redis state of paired nests synchronizes with MySQL during reset — desynchronization there most often breaks the schedule

A nuance that is important to check: two parallel nests (executor / customer) must be cleaned symmetrically. If one is cleaned earlier — the second user will remain in the chat without a conversation partner. This is likely the source of the bug.

aiogram v3, asyncio, and analyzing someone else's code are my daily work. Webhooks, Redis state, and MySQL connections are the stack for this task.

I work through Safe: first, I will locally analyze the algorithm of the cleaner and show where exactly the logic breaks — then the fix on the server. To start, access to the repository and SSH will be needed.

Question regarding the essence: is the cleaner currently triggered through APScheduler/Cron or is it an asyncio task inside the bot? Expand

Budget: 1500 UAH Deadline: 2 days

The task is basically clear: we need to fix the background task (cleaner) for the chats, as it is getting off schedule and not counting the normal 7 days.

I have worked with this stack (aiogram v3, asyncio, redis, mysql), and I have experience with user bots and background processes.

I am ready to quickly resolve your issue.

Budget: 1500 UAH Deadline: 1 day

Hello, Sergey.

Judging by the description, the problem lies either in the asynchronous task of the scheduler (when background tasks fail due to unhandled errors) or in the incorrect selection of the last activity dates from MySQL — it's hard to say for sure, we need to take a look. I can access the server and study the code carefully, so as not to disturb anything else.

Could you let me know if the cleaner runs within the bot's process through asyncio/APScheduler, or is it a separate script under systemd/cron?

I actively write in Python (including aiogram v3, MySQL, Redis, and async) with several years of experience, I have no problems understanding someone else's code and have experience in bot development — you can check the reviews.

Message me privately, and we can discuss the details, and I will get started on the task right away.

Budget: 1500 UAH Deadline: 2 days

Hello, Sergey. The irregular cleaning in services on aiogram v3 with the "nor" queue is most often explained by the fact that the cleaner keeps a 7-day count in the process memory, through an asyncio task or sleep cycle, and any bot restart or deployment resets these timers without a trace in the logs, causing some chats to simply drop out of the schedule. I will check whether your cleaner operates this way or through an external scheduler, and where the last activity timestamp comes from, whether from MySQL or Redis, as this affects where the logic breaks.

If the reason lies in the timers, I will move the check to a periodic idempotent pass over last_activity in MySQL with verification in Redis, which survives the restart and does not touch paired chats and the application queue; I will only change the cleaner itself. Before deploying to production, I will test the fix on a couple of test nors with artificially aged activity to see that the bot releases participants and returns the chat to the queue as intended.

Regarding payment and deadlines, 1500 UAH, 2 days from the moment of access to the server and logs. Please let me know if there is SSH and a test environment or a copy of the database to check the fix not on live chats?

Budget: 3800 UAH Deadline: 5 days

Understood the essence: the cleaner of the burrows should check the deal and activity for 7 days on schedule, but right now it is breaking down, and the queue is not being cleared in time.

I will connect to the server, analyze the cleaner's code and the scheduler, find where the condition is failing in MySQL and Redis, and make precise adjustments without touching the logic of the chats and burrows.

Ready in 5 days. Is the cleaner currently a separate worker or through cron?

Budget: 18000 UAH Deadline: 4 days

We already have almost ready solutions for Telegram bots with queues, roles, background tasks, and AI automation, so we can quickly access the current code and carefully fix the problem.

Regarding timelines - the target is 2-4 days after access to the server and repository.
Regarding budget - 18,000 UAH for diagnostics, fixing, and testing in a working scenario.

Look, there's a nuance here - in such tasks, it's important not just to fix the cleaner but to check the entire chain:
> creating burrows
> queuing
> checking transactions and activity for 7 days
> removing participants
> returning the chat to the queue
> absence of side changes in the current chat logic

We do not change the operation of chats and the main mechanics. We conduct a targeted analysis of the current algorithm, log the reasons for the failure, fix the schedule or conditions for cleaning, and then test on the server or on a copy of the database.

For an accurate assessment, we need to clarify 2 points:
> Is the cleaner currently implemented through a separate asyncio process, cron, celery-like queue, or within the bot itself?
> Is there a test server, or can we only work on the production one with a backup of the database?

Similar cases:
> https://business.ingello.com/vorfahr - automation of a service with AI and complex process logic
> https://business.ingello.com/fractal - agency and automation processes where queues and reliable task execution are important
> https://systems-fl.ingello.com - Ingello Systems profile for automation and development projects

In touch, we can start with a short diagnostics of the current code and logs =) Expand

Budget: 2000 UAH Deadline: 1 day

Hello.

I can handle the current implementation of "nests" and fix the cleaner's operation without changing the existing chat logic.

I work with Python, asynchronous code, aiogram 3, aiohttp, MySQL, and Redis. First, I will check the full cycle of chat operations: creating paired nests, assigning a client and executor, recording activity, deal status, cleaning inactive chats, and returning free nests to the queue.

I will separately check:

* why the cleaner does not run on schedule;
* the correctness of determining seven days of inactivity;
* whether an active or completed deal is taken into account;
* synchronization of two parallel chats;
* the operation of the Redis queue;
* re-adding one nest to the queue;
* parallel execution of several instances of the cleaner;
* the server's time zone;
* handling errors from the Telegram API;
* logging of cleaning and reasons for skipping chats.

I will make minimal changes specifically to the problematic module to avoid affecting other bot functionality. Before making corrections, I will document the current logic, create a backup of the changes, and test the operation on test nests.

After completion, I will provide a brief report: what the cause was, which files were changed, how the algorithm now works, and how to check the cleaner on the server. Expand

Budget: 3500 UAH Deadline: 3 days

Good day, Serhiy!

My name is Roman, and I have carefully reviewed the description of your project regarding the setup of a Telegram bot on aiogram v3 with an issue in the chat functionality, specifically with the cleaner "Nir." I have significant experience working with aiogram v3, asynchronous programming (asyncio), and aiohttp, as well as with MySQL and Redis databases, which are key technologies for your bot. I understand that the correct operation of the cleaner, which returns unused "Nirs" to the queue, is critically important for the efficiency of your system for interacting with clients and performers. My approach focuses on a thorough analysis of the existing code, which will allow me to localize and eliminate the cause of the cleaner's incorrect operation without affecting other functional parts of the bot, as you mentioned.

My action plan is as follows: first, I will conduct a detailed study of the logs and the current implementation of the cleaner on your server to accurately identify the bug that leads to its incorrect operation and untimely cleaning of chats. Second, I will develop and test a fix that will ensure the cleaner operates according to the 7-day period algorithm and reinstates chats back into the queue. Third, I will conduct comprehensive testing to ensure that the fix does not introduce new errors and that all other mechanisms of the bot, including the creation of "Nirs" and parallel chats, function flawlessly. I am responsible, punctual, and always pay attention to detail, which will allow me to ensure the stable and reliable operation of your bot.

The cost of the work is 3500 UAH, and the deadline is 3 working days. I am ready to provide links to similar completed projects in private messages so you can assess my level of expertise. As a pleasant bonus, I offer free 7-day support after the project is delivered, so you can be confident in the stable operation of the corrected functionality. Do you already have any assumptions about the possible cause of the bug in the cleaner that could expedite the diagnosis?

Budget: 1500 UAH Deadline: 1 day

Good day, Serhiy!

I am ready to take a look directly on the server. From the description, it seems like one of three typical reasons: the cleaning task is hanging on asyncio.sleep in a loop and quietly dying without logging during a restart/network delay; or the cleaning transaction is committing in the wrong connection from the MySQL pool, so other parts of the bot see stale data; or Redis is holding a TTL marker for the schedule that is expiring incorrectly. I know where to look in each case.

The stack — aiogram v3, asyncio, MySQL + Redis together — is my main profile; I have worked with such a combination in a production project with live monitoring via Telegram.

Question: is there SSH access to the server and logs from the last cleaning task failures? Without a budget, I am aiming for 1500–2500 UAH, 1–2 days, depending on the readability of the code.

github.com/kamedashe

Bogdan Expand

Budget: 4000 UAH Deadline: 2 days

It seems that the chat cleaner is not working on schedule — the issue lies in the asynchronous scheduler (likely the asyncio loop or Redis queue). I will quickly diagnose, fix it directly on the server, with a backup and rollback. Plan: 1) Analyze the cleaner code and its triggers; 2) Correct the scheduling logic (if necessary — replace with apscheduler or check coroutines); 3) Test in the working environment. I have experience with complex asynchronous systems (for example, an automated Twitter manager using Selenium + Python) [1]. Please provide access to the server and clarify: what should the cleaning schedule be? Is there already a testing environment? Example of work: https://freelancehunt.com/showcase/work/programmnoe-obespechenie-dlya-twitter-avtomatizirovannoe-upravlenie/1874481.html

Price: 4000 UAH
Deadline: 2 days

Budget: 1500 UAH Deadline: 1 day

Hello, I have over 5 years of experience in bot development, message me and I'll help! I will quickly solve your problem)

Budget: 3400 UAH Deadline: 4 days

The task is clear: the burrow cleaner works with bugs, does not follow the schedule, does not free chats after 7 days of inactivity, and does not return them to the queue.

I will connect to the server, analyze the current logic of the scheduler (cron/asyncio task) and the conditions for checking the last activity in MySQL, find where the schedule breaks and why the removal of participants from the chat does not trigger. I will make targeted corrections without changing the rest of the chat logic, paired burrows, and Redis queue.

Deadline: about 4 days. Please clarify access to the server and repository after the start.

Budget: 1100 UAH Deadline: 1 day

Hello.

I have extensive experience in this field, so I am ready to start as soon as the discussion is over.

Budget: 1000 UAH Deadline: 1 day

Hello.
I will thoroughly analyze the current implementation of the "cleaner" mechanism in the context of the aiogram v3 architecture, asynchronous processes, and interaction with MySQL and Redis. I will pay special attention to identifying incorrect conditions, race conditions, or errors in data handling that lead to violations of the chat cleaning logic and their return to the queue. I will implement corrections, ensuring precise adherence to the cleaning schedule and the stability of existing chat functions, using idempotent operation patterns. I have significant experience in developing and optimizing background processes for Telegram bots, as well as ready-made templates for testing and deploying similar fixes. I suggest discussing all implementation details, final budget, and timelines in private messages.

Budget: 700 UAH Deadline: 1 day

Hello! I am ready to quickly connect, understand your code, and fix the bug in the Telegram bot right now.

I am a developer specializing in asynchronous Python and automation. I have solid practical experience working specifically with aiogram v3 (including working with FSM, middlewares, and custom filters), and I also have a great understanding of the logic of asynchronous requests through aiohttp, working with webhooks, MySQL databases, and caching in Redis.

I am excellent at reading and refactoring someone else's code. I will do everything quickly and neatly, without breaking the current architecture of the service. The price is low since I am just starting on this profile and working for my first review and rating.

I am ready to move to a personal chat right now.

Budget: 1000 UAH Deadline: 1 day

Good day, I am ready to complete your task quickly and efficiently. I have extensive experience in creating various bots. Please write to me in private messages to discuss the details. I would be happy to help :)