Cron, interval, daily, weekly, custom — every kind of recurring Salesforce data movement, scheduled locally on your Mac. No Windows VM. No cloud orchestrator. No Lambda fees.
The official Salesforce Data Loader supports scheduling — but only on Windows via command-line invocation through Task Scheduler. The Mac version has no scheduling capability at all. dataloader.io supports scheduling but costs $299 per user per month for the Enterprise tier that includes it. Jitterbit's Mac version was discontinued in 2024. The result: Mac-based Salesforce admins have been scheduling jobs through hacky workarounds (Windows VMs, cloud Lambda functions, custom Python scripts) for years.
QueryFlow's scheduler is built into the app and runs using macOS background task APIs. Any query, pipeline, or Flow Book can be scheduled with cron, interval (every N minutes/hours), daily at a specific time, weekly on specific days, or monthly on specific dates. The scheduler runs while QueryFlow is open or while your Mac is awake — there's no separate daemon to install or maintain.
Hourly Lead imports from a warehouse during business hours: Trigger = cron 0 9-17 * * 1-5 (9 AM to 5 PM weekdays). Daily Opportunity sync from Postgres at 6 AM: Trigger = Daily at 06:00. Weekly Account hierarchy refresh from a CSV file: Trigger = Weekly, Monday 8 AM. End-of-month financial sync from Snowflake: Trigger = Monthly, last day at 11 PM. All of these are 30-second configurations in QueryFlow.
macOS handles background tasks with a catch-up model. If a scheduled job was supposed to run at 6 AM and your Mac was asleep, QueryFlow's scheduler runs the missed job within seconds of you opening the lid. For mission-critical scheduling where the Mac absolutely must be awake at scheduled times, configure macOS Power Schedule (System Settings → Battery → Schedule) to wake the Mac at the relevant times. QueryFlow's scheduler then runs immediately on wake.
Every scheduled job has configurable retry behavior. Set the number of retry attempts (default 3), backoff interval (default exponential starting at 30 seconds), and what counts as a failure (Salesforce-side errors, network errors, validation failures). Failed runs send a macOS notification by default. Optionally, configure email alerts or webhooks to a Discord channel or Slack workspace for team visibility.
The Observatory dashboard shows every scheduled job with run history, success rates, average duration, and last-run timestamp. Click into any individual run to see the full execution log, the rows processed, any errors with full context, and the SQL or pipeline that ran. This is the visibility layer Salesforce Data Loader has never had on Mac.
The standard cloud pattern for Salesforce scheduling involves AWS Lambda + EventBridge + IAM roles + CloudWatch Logs + Salesforce credentials in Secrets Manager. The total cost is usually $50-$200/month for a small team plus the engineering time to maintain it. QueryFlow's local scheduler costs $299.99/year flat and requires zero infrastructure. For most Salesforce admin workloads, the cloud pattern is dramatically over-engineered.
The scheduler runs in a lightweight background process that persists when QueryFlow's main window is closed (as long as the app is still running in the dock or menu bar). For absolute reliability, configure QueryFlow to launch at login in System Settings → General → Login Items so it starts automatically with your Mac.
Two options. First, configure macOS Power Schedule (System Settings → Battery → Schedule) to wake the Mac at scheduled times. Second, accept the catch-up model where missed jobs run on the next wake — this is fine for jobs where end-of-day data freshness is acceptable. For 24/7 SLA-bound jobs, neither QueryFlow nor a desktop Mac is the right architecture.
Yes. The scheduler runs jobs concurrently by default. If two jobs are scheduled at the same time, both start in parallel. For jobs that must run sequentially (e.g., load Accounts first, then load Contacts that reference those Accounts), configure pipeline dependencies in the schedule settings.
Yes — scheduled jobs consume the same Salesforce API limits as manual runs. A daily job that loads 5,000 Contacts consumes the same API calls whether you run it by hand or it runs automatically. Monitor your consumption through QueryFlow's Observatory dashboard or Salesforce Setup → System Overview.
Yes. Each scheduled job has an Enable/Disable toggle on its card in the Schedules panel. Disabled jobs preserve all their configuration but do not run on their trigger. Re-enable when you want to resume. This is useful during deploys, maintenance windows, or holidays.
14-day free trial. Schedule your first recurring Salesforce job and walk away — no AWS account, no Windows VM, no $299/month plan.