Budget: 200 EUR Deadline: 7 days
Yuliia, I can help isolate these filter bugs quickly. I work with JavaScript and Laravel in production, so I’m used to tracing query issues, reproducing edge cases, and fixing them without breaking live flows. I’ll review the Next.js/Supabase code, check pagination and record limits, test the affected filters, and deploy stable fixes. I’m available now and can share a clear delivery estimate after a quick code review. If you want, I can start right away.
Budget: 150 EUR Deadline: 4 days
Hi Yuliia. I work exactly with this stack — Next.js/TypeScript + Supabase + Vercel — and your three issues have familiar root causes:
— "Failed to query editais: Bad Request" on certain filters: usually a malformed Supabase query (wrong operator or unescaped value on a filter param). I'll trace the exact failing request and fix the query builder.
— "Not reviewed" filter failing as records grow: the classic Supabase default 1000-row limit / range issue — needs proper .range() pagination or a keyset approach so it scales.
— Pagination / query limit: same family — correct limits + server-side pagination.
Plan: reproduce each on a branch, apply stable fixes, test the affected filters, deploy to production on Vercel. Around 150 EUR, 3-4 days. Ready to look at the repo and confirm the exact scope.
Budget: 2000 EUR Deadline: 7 days
Hello, I worked on tender analysis — processing 50K+ records with filtering and pagination on Supabase/PostgreSQL, solving similar issues with query limits.
Can you clarify which specific filters are causing the "Bad Request" — are these specific combinations of parameters or does the problem arise with a certain number of records in the table?
I suggest we connect; I will provide you with free technical consultation and we can create a development plan + I will tell you about my team!
Budget: 111 EUR Deadline: 1 day
I am a NextJs, React, NestJs developer. I am ready to take on this task.
Budget: 8000 EUR Deadline: 3 days
The core problem is Supabase query limits and filter logic breaking under growing data in a live Next.js tender tracker.
My approach: first reproduce each bug locally against the real Supabase project (or a clone) to confirm root cause, then fix the "Bad Request" by auditing filter parameters being passed to PostgREST (likely an unsupported operator or oversized IN array), then address the "Not reviewed" filter by replacing a naive full-table scan with a proper indexed query plus cursor-based pagination instead of offset, which collapses under large row counts. Finally, deploy to Vercel and verify in production with the same filters that were failing.
The key risk is Supabase's 1000-row default limit silently truncating results rather than throwing an error, which can mask the real pagination bug. I'd add explicit range headers and test at multiple page depths.
Can you share the repo and roughly how many tender records are currently in the table the "Not reviewed" filter queries?
Budget: 25 EUR Deadline: 3 days
Hi Yuliia,
I can review the existing Next.js and Supabase codebase, reproduce the filter errors, and fix the underlying query or pagination issues without changing the current functionality.
I have experience with Next.js, TypeScript, Supabase, PostgreSQL, and Vercel deployments. I’ll also test the affected filters and confirm the production build after the fix.
I’m available to start immediately.
Estimated delivery: 1–3 days, depending on the codebase and logs.
Hiroshi
Budget: 100 EUR Deadline: 3 days
Hello, Yuliia!
Your stack is exactly what I work with every day: Next.js, TypeScript, Supabase, PostgreSQL, deployment on Vercel.
Regarding your bugs, I see the following directions:
— "Bad Request" on filters — this is often an incorrect request to Supabase (wrong filter operator or parameter type); we need to look at the specific request.
— A filter that breaks with an increase in records, and pagination issues — this seems related to Supabase limits (by default, it returns 1000 rows) and the lack of proper range/pagination.
I am ready to start by reproducing the bugs, finding the cause, applying stable fixes, testing the filters, and deploying to production.
Please send access to the code (or repository) — I will clarify the exact lines. I work through Safe.
Budget: 120 EUR Deadline: 3 days
Hi,
Two of the three issues likely share one root cause: Supabase returns max 1,000 rows per query by default. Once "Not reviewed" crosses that, the filter silently drops records — which also shows up as your pagination limit. The fix is proper server-side pagination via .range() with an exact count, not just raising the cap (that slows queries down).
The "Bad Request" on certain filters is separate — usually a malformed PostgREST query (unescaped value, type mismatch, or a bad .or()). I can only pin it down by reproducing the actual request, so I won't guess at it blind.
Since I'm new to your codebase, I'd keep it safe: reproduce all three on a branch, confirm root cause, then give you a fixed price before anything touches prod. Every fix ships through a Vercel preview so you verify it on real data before it merges live.
Supabase, PostgreSQL and Vercel are my daily stack, and query behavior at scale is my strong area. TypeScript/Next.js I read and work in comfortably.
I can start now. Delivery: 2–3 days. Price: $120 for all three, confirmed once I've seen the repo.
Budget: 300 EUR Deadline: 2 days
Hello!!!
First, I will review your current code to understand why there is such a problem, make a stable fix, test the affected filters, and deploy it to production.
Feel free to reach out.
Budget: 70 EUR Deadline: 3 days
Hello!
I can help investigate and fix the filtering and query issues in the existing PNCP monitoring platform.
Based on the description, the problems may be related to Supabase query construction, handling of the “Not reviewed” condition, pagination, or query limits as the number of records grows. I would first reproduce the reported cases, review the affected Next.js and Supabase logic, then apply and test stable fixes before deploying them to production.
I am comfortable working with backend logic, PostgreSQL queries, filtering, pagination, and existing codebases. I also actively use modern development tools to analyze and test changes efficiently.
My preliminary estimate is 3,500 UAH and approximately 3 working days.
The stated cost and timeline are preliminary. After reviewing the necessary project details and reproducing the issues, I will be able to confirm the final price and exact delivery time.
Budget: 250 EUR Deadline: 3 days
Hello! The described issues are classic pains of projects that have grown from the initial Supabase architecture and have faced performance degradation due to increased data volume in PostgreSQL. As a Senior Full-stack engineer with experience in developing high-load SaaS platforms on Next.js, TypeScript, and Supabase, I fully understand how to quickly and painlessly fix these bugs.
Why these problems occurred and how I will solve them:
* "Invalid request" error: This often arises from incorrect URL request formation, exceeding string length limits with a large number of filters, or mismatched TypeScript data types in the Supabase client. I will find and fix the vulnerable method.
* "Not viewed" filter and pagination: Supabase has a hard limit on sampling (offset/limit) of up to 1000 records by default. As the PNCP database grew, the usual `offset` stopped coping or hit limits. I will optimize the PostgreSQL query, add the correct indexes on the view status column, and if necessary, switch pagination to a faster `cursor-based` approach (keyset pagination).
Commercial terms:
* Cost: $250 – $350 USD (final amount after a quick audit of your repository).
* Deadline: 2–3 days for complete resolution of all three issues, testing, and deployment to production on Vercel.
* Availability: Ready to start working today.
I have deep expertise in optimizing heavy SQL queries and working with Vercel infrastructure. You can familiarize yourself with my architectural approach on my website: https://mcarrow.online
Let's move to personal messages: you will provide access to the code (or show the problematic areas), and I will promptly return your monitoring system to a stable working state!
Best regards,
Serhiy Makarov
Budget: 228 EUR Deadline: 3 days
Yuliia, I see the PNCP tender system is struggling with data load, specifically regarding the Supabase query limits and filter performance. It looks like the growing dataset is causing timeouts or payload issues that the current pagination logic isn't handling correctly.
I will debug the filter states and optimize the Supabase queries to ensure the 'Not reviewed' filter functions efficiently as the database expands. Once the query bottlenecks are resolved, I'll test the deployment on Vercel to ensure the fix holds under live conditions.
Could you confirm if the 'Bad Request' error happens consistently with specific search terms, or does it trigger randomly as the result set exceeds a certain count?
