Solid Queue Recurring Transactional Email with Rovela (2026): recurring.yml + Idempotency-Key per Window

Solid Queue owns the schedule — Rovela delivers the mail

Solid Queue is Rails’ DB-backed Active Job backend (default-friendly on Rails 8). Recurring tasks live in config/recurring.yml (or equivalent): cron-like schedules that enqueue jobs into Solid Queue for workers (bin/jobs / Puma plugin) to run. That fits digests whose body depends on live Active Record state at fire time rather than content frozen earlier with Rovela scheduled_at.

Distinct from Sidekiq-Cron, Hangfire, and delayed_job Recurring — this post is Solid Queue recurring.yml.

Rovela queues, DKIM-signs, and delivers when your job method calls POST https://api.rovela.dev/emails (Send Email API, Quick Start, Authentication). Solid Queue owns the cadence and “is due?” logic. Your job method owns aggregation, secrets for sending_access, and a stable Idempotency-Key per schedule window. Rovela only delivers.

This guide wires Solid Queue → job method → Rovela that:

1. Declares a config/recurring.yml entry that enqueues DailyDigestEmailJob on a cron schedule, with Solid Queue workers running
2. Keeps ROVELA_API_KEY (sending_access), MAIL_FROM, and recipients in server-only config — never in browsers, SPA bundles, or a public Git tree
3. Aggregates a digest / report for the current schedule window inside the job method
4. Sends via Rovela with a window-scoped Idempotency-Key
5. Survives retries, restarts, and multi-worker fleets without duplicate mail

Rovela does not create Solid Queue schedules, workers, or storage. Solid Queue owns schedule → enqueue/fire → execute. Your job method owns query → map fields → POST /emails. Rovela owns delivery.

Distinct from:

• Quartz Scheduler Transactional Email — Java Quartz
• node-cron Transactional Email — node-cron
• NestJS Schedule Cron Email — NestJS @Cron
• Laravel Task Scheduler Email — Laravel Schedule::
• APScheduler Cron Email — APScheduler
• Spring @Scheduled Email — Spring @Scheduled
• Resque-scheduler Email — Resque-scheduler
• RQ Scheduler Email — RQ Scheduler
• delayed_job Recurring Email — delayed_job
• Hangfire Recurring Jobs Email — Hangfire
• Sidekiq-Cron Transactional Email — Sidekiq-Cron
• Celery Beat Transactional Email — Celery Beat
• Agenda.js Scheduled Jobs Email — agenda
• BullMQ Repeatable Email — BullMQ
• Temporal Schedule Email — Temporal
• Trigger.dev Cron Email — Trigger.dev
• Inngest Cron Transactional Email — Inngest
• Kubernetes CronJob Email — K8s CronJob
• Vercel Cron Digest Email — Vercel cron
• Scheduled Email Sending — scheduled_at

Also distinct from one-shot Active Job mailers — this post is the recurring.yml path only.

What Solid Queue schedules vs what Rovela sends

Concern	Owner
recurring.yml cron / class / queue	Solid Queue recurring tasks
DB-backed queue + workers	Solid Queue (bin/jobs)
Active Job #perform	Your job class
Server secrets for ROVELA_API_KEY (sending_access)	Process / worker env / secret store
Query DB / APIs for the window	Your job method
Render HTML + text	Your job method
POST /emails, DKIM, queue, bounces	Rovela
Idempotency-Key = solid-queue-daily-digest:{yyyy-mm-dd}	Your job method

A 200 from Rovela means accepted and queued, not “already in the inbox” (Quick Start).

Solid Queue constraints that shape the email job

• Dispatchers / workers must stay up (bin/jobs or Puma plugin) — recurring evaluation is part of Solid Queue’s runtime.

• Use explicit task keys in recurring.yml so deploys replace cleanly.

• Timezone: set schedule timezone per Solid Queue / recurring docs for your Rails version.

• Single recurring definition — avoid duplicating the same logical digest under two keys.

• Prefer Sidekiq-Cron only if you already standardized on Redis Sidekiq.

• Keep sending_access server-only. Store ROVELA_API_KEY in environment / vault — never in client apps or public Git (Authentication).

• Prefer HTTPS POST /emails. Outbound SMTP from a worker is a poor fit (Email API vs SMTP).

When to use Solid Queue + POST /emails (not scheduled_at)

Use Solid Queue → live send when:

• The HTML must include fresh metrics at fire time
• You already run Solid Queue and want schedules next to the same workers
• You need cron-like digests without adopting a separate SaaS scheduler
• One (or a few) transactional messages go to ops / founder / customer addresses looked up at run time

Use Rovela scheduled_at when the body is already correct and you only need “deliver later” without a running scheduler (Scheduled Email Sending). Prefer Solid Queue when you want DB-backed jobs without Redis; prefer Sidekiq-Cron when Redis Sidekiq is already core infra.

Prerequisites

1. A verified sending domain in Rovela. Unverified from domains are refused with 400 (Quick Start).
2. An API key shaped like re_…. Prefer sending_access for the worker (Authentication).
3. Rails 8+ (or Rails with solid_queue installed), recurring.yml configured, jobs process running.
4. Config: ROVELA_API_KEY, MAIL_FROM, DIGEST_TO.
5. An Active Job class (< ApplicationJob) that POSTs to Rovela.

Register the schedule

config/recurring.yml (shape illustrative — match your Solid Queue / Rails version):

production:
  daily_digest_email:
    class: DailyDigestEmailJob
    queue: mailers
    schedule: every day at 9am UTC
    # or a cron form supported by your version, e.g. "0 9 * * *"
  ops_pulse_email:
    class: OpsPulseEmailJob
    queue: mailers
    schedule: every 15 minutes

Run workers / dispatcher:

bin/jobs
# or enable the Solid Queue Puma plugin in production

Confirm in Solid Queue’s recurring UI / tables that daily_digest_email is registered with the expected schedule.

Job method that calls Rovela

class DailyDigestEmailJob < ApplicationJob
  queue_as :mailers

  def perform
    day = Time.now.utc.strftime("%Y-%m-%d")
    idempotency_key = "solid-queue-daily-digest:#{day}"
    stats = { signups: 12, paid: 3, incidents: 1 } # replace with AR aggregates
    to = ENV.fetch("DIGEST_TO").split(",").map(&:strip).reject(&:empty?)
    subject = "Acme daily digest — #{day}"
    text = "Signups: #{stats[:signups]}\nPaid: #{stats[:paid]}\nIncidents: #{stats[:incidents]}"
    html = "<h1>Daily digest — #{day}</h1><ul>" \
      "<li>Signups: <b>#{stats[:signups]}</b></li>" \
      "<li>Paid: <b>#{stats[:paid]}</b></li>" \
      "<li>Open incidents: <b>#{stats[:incidents]}</b></li></ul>"

    Rails.logger.info({ msg: "solid_queue digest", day: day, idempotency_key: idempotency_key }.to_json)

    uri = URI("https://api.rovela.dev/emails")
    req = Net::HTTP::Post.new(uri)
    req["Authorization"] = "Bearer #{ENV.fetch('ROVELA_API_KEY')}"
    req["Content-Type"] = "application/json"
    req["Idempotency-Key"] = idempotency_key
    req.body = JSON.generate(
      from: ENV.fetch("MAIL_FROM"), to: to, subject: subject, html: html, text: text,
      tags: { kind: "solid-queue-daily-digest", day: day, platform: "solid-queue" }
    )
    res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true, open_timeout: 10, read_timeout: 30) { |h| h.request(req) }
    raise "Rovela #{res.code}: #{res.body}" unless res.is_a?(Net::HTTPSuccess)
    Rails.logger.info({ msg: "rovela accepted", emailId: JSON.parse(res.body)["id"], day: day }.to_json)
  end
end

Window-scoped Idempotency-Key

Rovela’s Idempotency-Key (up to 256 characters) makes a retry of the same send within 24 hours return the original response instead of mailing again (Send Email API). That matters because:

• Retries re-enter the job after 5xx / timeouts
• Crash after Rovela 200 but before the job is marked succeeded can redeliver
• Queue lag can shift wall-clock — key off the business schedule window, not millisecond now
• Multi-tenant jobs need tenant ids in the key

Recommended keys:

Key	Use when
solid-queue-daily-digest:{yyyy-mm-dd}	One ops digest per UTC day
solid-queue-ops-pulse:{yyyy-mm-dd}T{HH}-{MM}	/15 or hourly crontab (bucket to the window)
solid-queue-tokyo-ops:{yyyy-mm-dd}	Local-TZ morning digest
solid-queue-weekly-report:{yyyy}-W{ww}	One founder report per ISO week
solid-queue-tenant-digest:{tenantId}:{yyyy-mm-dd}	Per-tenant job args

If you mail many personalized digests in one job, prefer per-recipient keys (or POST /emails/batch for up to 100 non-template messages — batch rejects template / topic_id by design).

Attach secrets and verify the schedule

1. Set ROVELA_API_KEY (sending_access), MAIL_FROM, DIGEST_TO on the process that runs the scheduler/worker.
2. Confirm the schedule entry is registered with the expected cron and timezone.
3. Confirm workers are online.
4. Wait for the next tick, or trigger once in non-prod while keeping the window key stable.
5. Check logs for idempotencyKey + Rovela emailId. Optionally correlate later with Rovela webhooks.

Prefer sending_access on production senders — never full_access. Never log API keys. Rotate Rovela by create-then-revoke.

Failure modes and how to handle them

Symptom	Likely cause	What to do
Cron never fires	Scheduler/worker down	Keep the scheduling process always on
Double digests	Multiple schedulers / replicas	Single leader or distributed lock / persistent store
Wrong wall time	Assumed UTC / wrong timezone	Set timezone explicitly
Duplicate digests after retries	Unstable key / keyed by ms now	Use window-scoped keys; Idempotency-Key collapses duplicates within 24h
Rovela 401	Bad / missing ROVELA_API_KEY	Fix server env; confirm sending_access
Rovela 400 naming a domain	MAIL_FROM domain not verified	Verify the domain under Rovela Domains
Rovela 429	Rate limit	Raise/retry; keep the same Idempotency-Key
Secrets in Git	Key committed	Keep only in env / vault

Production checklist

• Verified Rovela sending domain; MAIL_FROM matches it
• ROVELA_API_KEY is sending_access, in worker env / vault only
• Scheduler + workers always running as documented for Solid Queue
• Documented cron + timezone
• Rovela send uses a window-scoped Idempotency-Key
• Logs show successful emailId without printing secrets
• Alerts on consecutive job failures / scheduler down
• Optional: Rovela webhooks for email.bounced / email.complained on digest recipients

FAQ

Can the scheduler call Rovela without a job method? No usefully — the scheduler only wakes your code. Your method must aggregate live data and keep sending_access local. Rovela does not host your scheduler or workers.

Should I use Rovela scheduled_at from the job? Usually no. If the scheduler already fires at send time with a live body, call POST /emails immediately. Use scheduled_at when you accept the message now and want Rovela to deliver later without another wake (Scheduled Email Sending).

What key scope does sending_access cover? Enough to queue mail via POST /emails / batch. Reading messages, rescheduling, and cancel need full_access or a dashboard session (Send Email API, Authentication). Keep the worker on sending_access.

Does a 200 mean the founder already got the digest? No — it means Rovela accepted and queued the message. Use GET /emails/:id, events, or webhooks for delivery state (Quick Start).

Why both scheduler retries and Rovela Idempotency-Key? The scheduler retries the job when your code fails. Rovela’s key collapses duplicate sends if the HTTP call succeeds twice in the same window (or times out after Rovela accepted). You want both layers.

Ship the recurring job; let Rovela deliver

Register the Solid Queue schedule with an explicit cron and timezone, put live aggregation and POST /emails in the job method, scope Idempotency-Key to the schedule window (and tenant), and keep sending_access server-only. Solid Queue wakes on time; Rovela delivers the transactional mail.