AutoVerse Workflow Controller icon

AutoVerse Workflow Controller

Enterprise workflow orchestration, execution control, and monitoring for n8n

Actions44

Workflow → Message Freshness Guard

AI-generated

Summary

Evaluates whether an incoming message is fresh enough to process for the selected workflow, using the workflow’s stored pause/activation cutoff. Returns a decision only; it does not alter the workflow or message.

Inputs

  • Workflow Selection (required) — Choose a workflow from the list, multiple workflows, the current workflow, or a workflow URL/ID. Although multiple IDs can be entered, this operation evaluates only the first resolved workflow ID.
  • Event Timestamp Expression (required) — A resolved message/event timestamp, such as a Unix timestamp in seconds or milliseconds, or a date string. Invalid or empty timestamps are treated as stale.
  • Message ID Expression — An optional resolved message ID echoed in the result for logging or downstream deduplication.

Output shape

A single result item containing workflowId, optional messageId, shouldProcess, stale, reason, eventTimestamp, optional eventTimestampIso, and dropBefore.

Messages dated before the workflow’s stored dropBefore timestamp are stale with reason event_before_last_activation. If no valid cutoff has been stored, valid timestamps are considered processable. An invalid timestamp returns shouldProcess: false, stale: true, and reason: invalid_event_timestamp.

Links

Discussion