Production Pulse · 2 / 8

Add a daily review timer

Keep the frequent heartbeat and add an independent daily diagnostic.

YOUR TASK

Make this happen

3 steps

Add integration_actor_timer.daily_review, name daily_review, with cron schedule 0 6 * * * and source return { review = true }.
Connect both timers in actor.cococo; keep the five-minute heartbeat and add its 15s jitter.
Check both schedules. The daily timer is a local diagnostic, not another remote signal.

THE IDEA BEHIND IT

Build on the working integration

Start with the previous solution. Add the next capability in actor.cococo, timer.cococo, daily.cococo. Connect the new components through their parent lists; supplied scripts and contracts remain read-only fixtures.

Interval or cron

A timer has exactly one schedule. Keep every = 5m for heartbeat; add a separate cron = "0 6 * * *" timer for a daily 06:00 UTC diagnostic. This introduces an independent schedule rather than replacing heartbeat.

Why jitter helps

Jitter spreads timer starts so many installations do not all hit a service together. It must be at most one hour and no greater than an interval timer’s interval. Here 15 seconds is safely below five minutes. Validation does not wait for or run a timer.

Checks cover structure and lesson requirements. Scripts and platform behaviour are not executed.

Actor and Action reference ↗Schema client reference ↗

This lesson starts with the previous working solution. Build and connect the next capability. Your earlier drafts are kept separately.

Read the starter files

main.cococo

integration_document "monitor" {
  integrationId = "com.academy.monitor"
  sdkVersion = "2.0"
  version = "1.0.0"
  description = "A small heartbeat integration"
  actor = integration_actor.monitor
}

actor.cococo

integration_actor "monitor" {
  timers = [integration_actor_timer.heartbeat]
}

timer.cococo

integration_actor_timer "heartbeat" {
  name = "heartbeat"
  schedule = { every = "5m" }
  source = "return { alive = true }"
}

daily.cococo

integration_actor_timer "daily_review" {
  name = "daily_review"
  # TODO: add schedule — see the task above.
  # TODO: add source — see the task above.
}

Supplied scripts and pinned contracts (read-only)

These fixtures explain the runtime behaviour being composed. They are included in validation but are not executed. The generated API definition is supplied, not an XML authoring task.

scripts/heartbeat.lua

return { alive = true }