Giving One AI Action Its Own Seven-Minute Deadline
A long model action kept an operation-specific waiting budget and caller cancellation, while transport headers and proxy limits remained separate boundaries
Reviewed by Dmytro Nasyrov on October 22, 2026.
We gave question generation a seven-minute waiting budget while ordinary gateway operations retained a 15,000-millisecond first-response deadline. That configuration did not mean generation had been measured at seven minutes. It expressed how long this particular operation was allowed to wait.
The application timer was only one limit
Beneath the application's abort timer, the pinned runtime imposed another relevant boundary: waiting for response headers through its bundled fetch implementation. Extending the application deadline did not necessarily extend that lower-level wait. The merged code used the package-provided fetch implementation with an agent whose header timeout was disabled for the long-deadline path. The application deadline remained in control. This was an operation-specific adapter in the recorded environment, not a recommendation to remove global timeouts from every request.
| Boundary | Recorded policy |
|---|---|
| Ordinary first response | 15,000 ms |
| Question-generation operation | Seven-minute configured budget |
| Long-path header wait | Dedicated adapter, with application deadline retained |
| Caller cancellation | Combined with the operation's deadline signal |
| Intermediate proxy | Must independently permit the intended wait |
Keep the exception narrow
Only the approved generation operation received the longer allowance. Ordinary requests retained their existing deadline and transport behavior. Authorization also remained in the path; a longer wait was not a new permission. The implementation combined the caller's cancellation signal with the deadline signal. A user leaving the operation should not be forced to wait for the entire configured budget merely because the model action can legitimately take longer than a normal read.
The adapter kept an abort signal after changing transports
Increasing the integer passed to ordinary fetch would not describe the historical implementation. It selected the package fetch path when the requested deadline exceeded the recorded bundled-header limit, constructed a dedicated Agent and combined the caller signal with its own timer. The central signal expression was:
const signal = init.signal
? AbortSignal.any([init.signal, controller.signal])
: controller.signal
patientAgent ??= new Agent({ headersTimeout: 0 })Disabling that Agent's header timer transferred responsibility to the application's deadline. It did not mean the request had no deadline. A caller abort could still end it early. The ordinary path retained the default transport when the requested budget was no longer than the recorded lower-level boundary. For the model operation, the adapter also read the small GraphQL response body before returning a platform Response. The ordinary first-response path had a different lifetime: after its headers arrived, the returned body could continue streaming. Treating the configured integer as an identical whole-body timeout for every operation would therefore misdescribe the adapter.
The timer fixture tested the edge, not a real model's speed
In the targeted test, fake timers advanced to one millisecond before the model deadline without the operation failing. The test then crossed the boundary and expected the abort. Separate assertions checked that the long path constructed an Agent with headersTimeout: 0 and that the ordinary path remained with the platform fetch.
Those assertions can reject a regression that aborts at the ordinary 15-second budget or the historical five-minute header boundary. They cannot establish the time an actual model takes to answer. Fake timer progress is not a latency sample, and the source's cold-start discussion is not a production percentile.
An allowlist associated the longer budget with generateBaselineQuestions. Existing authorization and field validation remained responsible for whether the operation could run. A timeout exception should follow the operation selected by that adapter rather than a browser-controlled promise that a request is expensive.
The editor retained existing questions on failure
Generation errors left the current question set in place. A failed attempt to create replacements did not justify clearing the curator's existing material. This connected the transport change to a visible preservation rule in the editor.
While waiting, the UI still had to distinguish that state from success. A generous deadline can make a slow operation tolerable while making a silent failure harder to interpret. It should not be presented as evidence that the generated questions are correct or ready for approval.
The shortest upstream budget could still win
An ingress or another intermediary could impose a shorter timeout. The frontend gateway's adapter did not establish those external settings. A complete rollout check must inspect the actual request path rather than stop at the code that created the abort signal.
Recorded local-cluster checking and targeted adapter tests support the implemented route and deadline selection. There is no published latency distribution, production timeout frequency or measurement showing that generation normally consumes the whole budget.
Historical behavior is not permanent API advice
Runtime behavior is pinned to the source snapshot for this fix. Before turning it into a general configuration recipe, inspect the versions and current transport documentation used by the target application. The exact lower-level default may change while the need to account for several waiting limits remains.
This case belongs to frontend gateway integration. Backend model startup and worker architecture are separate contributions. The boundary table helps locate which part of a long request a test or setting actually covers.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 14
No matches
Try a different keyword, change the topic or clear filters
-
How long have you been in business?
Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).
-
What services do you provide?
Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).
-
Where is Pharos Production located?
Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.
-
How big is your team?
Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.
-
What types of customers do you serve?
We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.
-
How is a custom software development company different from an agency?
A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.
Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.
-
How much does custom software development cost?
Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).
-
How long does it take to develop a custom software application?
Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.
-
What industries does Pharos Production serve?
Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.
-
Why hire a software development company instead of building in-house?
Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.
Factor In-house team Software development company Time to assemble 3-6 months (recruiting + onboarding) 1-2 weeks Upfront cost High (salaries, benefits, equipment) Lower (project-based pricing) Specialized expertise Limited to who you can hire locally Access to 90+ engineers across blockchain, AI, FinTech Scalability Slow (each new hire takes months) Fast (scale up or down per sprint) Long-term commitment Full-time employment contracts Flexible engagement models Risk High if key engineers leave Company ensures continuity and knowledge transfer For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.
-
What projects does Pharos Production not take on?
Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.
-
Why does Pharos Production use agile methodology?
We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.
This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.
-
When should you NOT hire a custom software development company?
Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.
In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.
-
What kind of projects has Pharos Production delivered?
Here are three anonymized examples from our recent delivery history:
FinTech startup - payment platform (MVP)
Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.Healthcare provider - patient portal (Full product)
Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.Crypto exchange - trading engine (Complex)
Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.
Stas Rysin is the Lead Frontend Developer at Pharos Production. His work covers the design system, reader interfaces and administration workflows of a professional learning platform for aesthetic medicine.
