Cron Next Runs

workflow.cron_next_runs

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0

No network

Overview

You send a valid cron expression, its dialect, an IANA zoneId and an explicit after instant. count defaults to 10 and inclusive defaults to false. Each occurrence carries instant, local datetime, offset and DST resolution metadata plus the tzdbVersion. This does not schedule jobs. A successful call costs 1 execution credit.

A validated cron string still needs a bounded, timezone-explicit next-run list.

Reliability

Powered by pinned cron-utils 9.2.1 and java.time. Search stops after 50 years. CRON_EXPRESSION_INVALID — trigger: the expression does not parse in the dialect; retryable: no; next: call workflow.cron_validate. CRON_ZONE_UNKNOWN — trigger: zoneId is not IANA or UTC; retryable: no; next: send Area/Location. CRON_NO_OCCURRENCE — trigger: nothing in the 50-year horizon; retryable: no; next: change the expression or after. CRON_LIMIT_EXCEEDED — trigger: count above 100 or expression above 1024 characters; retryable: no; next: lower the bound.

Context footprint

Returns at most 100 occurrence rows plus tzdbVersion. A successful call costs 1 execution credit.

When to use it

When a valid expression, zone and after instant must produce the next N instants.

When the expression is still unvalidated, or when you need a scheduler.

Scope

Note

Expands a valid cron expression into a bounded list of zoned occurrences.

Non-goals

Does not schedule or persist jobs
Does not apply calendars or holidays
Does not enumerate an infinite series

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysis

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input64 KB

How we handle your data

Sensitive input, safe output

What this means

This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response does not contain submitted content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
expression	string	Yes	Cron text, 1 through 1025 characters; runtime accepts at most 1024.
dialect	string	Yes	UNIX_5, QUARTZ_6_7, SPRING_6 or AWS_EVENTBRIDGE. There is no AUTO.
zoneId	string	Yes	IANA zone such as Europe/Brussels, or UTC. Abbreviations and offsets are refused.
after	string	Yes	ISO-8601 instant that starts the search, for example 2026-03-08T01:00:00Z.
count	integer	No	How many occurrences to return, 1 through 101; omit it for 10. Runtime accepts at most 100.
inclusive	boolean	No	When true, an exact match at after is kept; omit it for false.

Output schema

Field	Type	Required	Description
dialect	string	Yes	Dialect that was actually applied to this expression.
zoneId	string	Yes	IANA zone that was actually applied to the occurrences.
count	integer	Yes	How many occurrences were returned, 1 through 100.
inclusive	boolean	Yes	Whether an exact match at after was eligible.
occurrences	array	Yes	Occurrence rows in ascending instant order, 1 through 100 closed objects.
truncated	boolean	Yes	True when the search horizon ended before count occurrences were found.
tzdbVersion	string	Yes	IANA tzdb version this JVM linked for offset and DST resolution.
engine	string	Yes	Pinned cron-utils Maven coordinate used to expand the expression.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"workflow.cron_next_runs","input":{"expression":"0 12 * * *","dialect":"UNIX_5","zoneId":"UTC","after":"2026-01-01T00:00:00Z","count":2}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("workflow.cron_next_runs", {"expression":"0 12 * * *","dialect":"UNIX_5","zoneId":"UTC","after":"2026-01-01T00:00:00Z","count":2});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
CRON_EXPRESSION_INVALID	400	No	The request payload failed this skill's input validation.
CRON_ZONE_UNKNOWN	400	No	The request payload failed this skill's input validation.
CRON_NO_OCCURRENCE	412	No	The input is valid but cannot be processed as-is.
CRON_LIMIT_EXCEEDED	429	No	A size, quota, rate, or time limit was exceeded.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not schedule or persist jobs
Does not apply calendars or holidays
Does not enumerate an infinite series
Validating an invalid expression without next-run intent
Building a job runner

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "workflow.cron_next_runs",
  "input": {
    "expression": "0 12 * * *",
    "dialect": "UNIX_5",
    "zoneId": "UTC",
    "after": "2026-01-01T00:00:00Z",
    "count": 2
  }
}

Examples

Two UNIX noon runs after 2026-01-01T00:00:00Z in UTC

Inputjson

{
  "expression": "0 12 * * *",
  "dialect": "UNIX_5",
  "zoneId": "UTC",
  "after": "2026-01-01T00:00:00Z",
  "count": 2
}

Expected outputjson

{
  "inclusive": false,
  "truncated": false,
  "count": 2,
  "occurrences": [
    {
      "instant": "2026-01-01T12:00:00Z",
      "localDateTime": "2026-01-01T12:00",
      "offset": "Z",
      "dstResolution": "STANDARD"
    },
    {
      "instant": "2026-01-02T12:00:00Z",
      "localDateTime": "2026-01-02T12:00",
      "offset": "Z",
      "dstResolution": "STANDARD"
    }
  ],
  "engine": "com.cronutils:cron-utils",
  "tzdbVersion": "2026b",
  "dialect": "UNIX_5",
  "zoneId": "UTC"
}

Tip

After midnight on 1 January the next noon is that same day.

inclusive true keeps a midnight that lands exactly on after