Base44
testing
Scheduled Workflow Running at Wrong Times or Not at All
Your Base44 app has scheduled workflows (daily reports, weekly reminders, monthly billing) that either don't run at all, run at the wrong time, or run multiple times. A workflow scheduled for 9 AM runs at 2 AM, a daily digest never fires, or a monthly report generates three times in one day.
Scheduled workflows are the backbone of automated business processes. When they fire at wrong times, reports go out overnight when nobody reads them, reminders arrive at midnight, and billing processes run at unexpected intervals causing duplicate charges or missed payments.
The timezone issue is particularly common: you configure a schedule thinking it's in your local timezone, but the server interprets it as UTC, causing a consistent offset in all your scheduled tasks.
Error Messages You Might See
Scheduled workflow did not execute at expected time
Workflow ran at 02:00 UTC instead of 09:00 local
Multiple executions detected within same period
Cron expression validation failed
Scheduled task not found after deployment
Common Causes
- Timezone mismatch — The schedule is configured in your local timezone but the server runs in UTC, causing a time offset
- Cron expression wrong — The cron syntax has a common mistake like month/day-of-week confusion or using 0-indexed vs 1-indexed values
- Schedule not saved correctly — The UI shows the correct schedule but the saved configuration has a different value
- Overlapping executions — The workflow takes longer than the interval, causing multiple instances to run simultaneously
- Server restart clearing schedule — The scheduled task registration doesn't persist across server restarts or deployments
How to Fix It
- Verify the timezone setting — Check if your Base44 app's scheduler uses UTC or your local timezone. Adjust the scheduled time accordingly
- Test with a short interval first — Set the schedule to run every 5 minutes and verify it fires correctly before setting the actual interval
- Validate cron expressions — Use a cron expression tool (crontab.guru) to verify your expression means what you think it means
- Add execution logging — Log every workflow execution with a timestamp so you can verify when it actually runs
- Prevent overlapping runs — Add a lock or flag that prevents a new execution from starting if the previous one hasn't finished
Real developers can help you.
Matthew Butler
Systems Development Engineer @ Amazon Web Services
Kingsley Omage
Fullstack software engineer passionate about AI Agents, blockchain, LLMs.
Matthew Jordan
I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job.
Basel Issmail
’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems.
My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale.
In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals.
I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software.
Omar Faruk
As a Product Engineer at Klasio, I contributed to end-to-end product development, focusing on scalability, performance, and user experience.
My work spanned building and refining core features, developing dynamic website templates, integrating secure and reliable payment gateways, and optimizing the overall system architecture.
I played a key role in creating a scalable and maintainable platform to support educators and learners globally.
I'm enthusiastic about embracing new challenges and making meaningful contributions.
Jacek Rozanski
Senior PHP/Symfony developer and DevOps engineer with 20+ years of professional experience, running opcode.pl (web development agency, est. 2004).
Day job: I'm the sole backend developer at merketing company where I own and maintain 11 PHP/Symfony microservices on AWS (ECS Fargate, RDS, S3, CloudFront), handle the full CI/CD pipeline (Bitbucket Pipelines, Docker), and manage monitoring with Sentry and CloudWatch. These services handle high request volumes in production every month.
What I bring to AI-built apps:
- I audit and fix security issues (OWASP methodology), performance bottlenecks, and architectural problems in codebases generated by Cursor, Claude Code, Lovable, Bolt, and v0
- I refactor AI-generated prototypes into production-grade applications with proper error handling, testing, and clean architecture (SOLID, DDD, hexagonal architecture)
- I set up the infrastructure AI tools don't touch: AWS hosting, CI/CD pipelines, automated deployments, database optimization, monitoring, and alerting
- I integrate external services: payment providers, email systems, partner APIs, SSO/auth
Tech stack: PHP 8.x, Symfony, React, Next.js, PostgreSQL, MySQL, Docker, AWS (ECS, RDS, S3, SQS/SNS, CloudFront), Terraform, Supabase. I also use AI tools daily (Claude Code, Cursor) in my own workflow, so I understand both the strengths and the gaps in AI-generated code.
Based in Poland (CET timezone). Available for async work and calls during EU/US business hours.
Luca Liberati
I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture
Prakash Prajapati
I’m a Senior Python Developer specializing in building secure, scalable, and highly available systems. I work primarily with Python, Django, FastAPI, Docker, PostgreSQL, and modern AI tooling such as PydanticAI, focusing on clean architecture, strong design principles, and reliable DevOps practices. I enjoy solving complex engineering problems and designing systems that are maintainable, resilient, and built to scale.
Meïr Ankri
Full-stack developer specializing in React / Next.js / Node.js with 6+ years of experience. I've worked across various sectors including automotive (Reezocar/Société Générale), healthcare (Medical Link SaaS), and e-commerce (Glasman). I build web apps end-to-end, from architecture to production, with a focus on scalability, performance, and code quality. I also mentor junior developers and contribute to technical decisions and code reviews.
Victor Denisov
Developer
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why does my Base44 scheduled workflow run at the wrong time?
The most common cause is a timezone mismatch. If you schedule for 9 AM but the server uses UTC, and you're in EST (UTC-5), the workflow will run at 9 AM UTC which is 4 AM EST. Convert your desired time to UTC.
How do I verify when my scheduled workflow actually runs?
Add logging to the first step of your workflow that records the current timestamp. Then check the logs after the expected execution time to confirm when it actually ran.