Component

core/ai-agent/dify-worker-beat

The Dify task scheduler — the Celery beat process that puts the platform's periodic work on the queue at its due time: dataset re-indexing sweeps, expired-file and orphaned-document cleanup, workspace usage rollups, and scheduled application runs. It reads the schedule from the platform's relational model in the PostgreSQL backend wired through the `backend` uses-socket and enqueues onto the Redis-compatible broker wired through `cache`, where the task worker picks the work up; it never runs a task itself. Exactly one instance runs — two schedulers on one queue would enqueue every periodic task twice — so it renders as a single-replica stateless worker. It serves no port and nothing connects to it, so it publishes no provides contract.

Version

1.0.01.1.0

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:3812ead58933f23dbeda6a6bc3c93adb89a573f662bdd52497b7b215ea1c18af
Published
2026-11-10T10:07:54Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:a56ab8d795cb54087e27c5d295238b70714d4386398a440df5236c378e1e5172

Reference at this version

oci://hub.aggrega.ai/component/core/ai-agent/dify-worker-beat:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

No developer parameters declared.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
engine_versionstring1.17.0noDify API container image tag. The API server, the task worker and this scheduler run the same image, so a Release moves all three together.
log_levelstring (DEBUG | INFO | WARNING | ERROR | CRITICAL)INFOnoLog verbosity the scheduler emits.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

No output values declared.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

backend

Selector
component.aggrega.ai/category=datastore
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional password the scheduler presents to the backend this connection reaches, shared with that backend. When attached, supplies the backend password via the credential subsystem; unattached, the Recipe uses the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password.

cache

Selector
component.aggrega.ai/category=datastore
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
server_cafeature.aggrega.ai/kind=secretnofileyesOptional authority the scheduler checks the cache's certificate against while the cache publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and points the cache client and the task broker at the file. The build halts on a server_ca publishing no Secret name, and on one wired to a cache served without TLS. Fill it with core/referenced-secret.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

env

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy