Skip to content
veycera

Shipment stop is confirmed

1 checks · within 10 seconds after resolution

Review 1 policy decision
MonitoringApproved version 1Approved 54 min ago1 recorded outcomes

1 policy decision is unrecorded for approved version 1. Approval is retained; review before renewed approval.

What retained approval means

This retained or seeded approval does not prove that a person accepted its policy assumptions. Existing approval has been preserved without inventing decisions. New approval still requires acceptance on the version being approved.

Approved policy

When
A shipping ticket is resolved after the agent approves the request.
Verify
  • The provider confirms the referenced shipment is canceled
Within
10 seconds after the ticket is resolved. Observed unmet conditions become violated at that deadline; condition evidence still unknown after the deadline is indeterminate.
Missing evidence handling
Use the order explicitly named in the ticket. If that reference cannot be resolved, the result is indeterminate and needs review. No match is inferred from email or recency.
Accepted alternatives
No conditional exceptions are defined. Every check applies to each matching ticket.

Policy decisions

1 need acceptance on version 1

Accept, request a change, or defer. Each decision records who decided and which version it applies to.

  • This synthetic provider acknowledgment has a ten-second deadline; it is separate from the two-minute refund rule.Undecided
    Source and effect on the rule
    Source: template defaultNo historical sample behind itField: deadlineSeconds

    Changing it touches the deadline (currently 10 s after resolution). Recording a change does not alter monitoring: v1 keeps being enforced as written until the conditions are edited, which creates v2 and resets approval.

Edit rule and preview changes

Changes create a new unapproved version. Read the preview before saving; historical executions keep their original policy.

Basic settings

Change preview

No policy fields changed.

Saving creates version 2, resets approval, and stops new monitoring until that version's assumptions are accepted and it is approved. Existing execution evidence keeps its evaluated version.

Verify

Edit a check to change its requirement or Accepted alternatives. Other checks stay collapsed.

The provider confirms the referenced shipment is canceledEdit check 1
Check the shipment status
Technical field mapping

the shipment status is canceled

Amount fields ending in Minor use the currency's minor units.

Accepted alternatives · applicability

This check always applies. Use Advanced rule definition to add an applicability condition.

When and missing evidence handling

When

A shipping ticket is resolved after the agent approves the request.

The existing trigger is retained when editing this rule.

Missing evidence handling

The existing correlation rule is retained. A missing required order reference remains indeterminate; unknown condition evidence is never a guessed success.

Advanced rule definition

Edit the supported condition JSON, including identifiers and exceptions. Trigger and correlation fields remain unchanged by this editor.

Review changes and save
Rule sources and technical definition

In this synthetic example, the provider must confirm an approved stop-shipment request within ten seconds after its support ticket is resolved.

  • Synthetic overdue provider acknowledgment example · template

    A queued shipment-stop request requires provider confirmation within ten seconds.

Advanced rule definition (JSON)
{
  "id": "ctr_yc_shipment_confirmation_yc-recording-v1",
  "tenantId": "yc-recording-v1",
  "name": "Shipment stop is confirmed",
  "description": "In this synthetic example, the provider must confirm an approved stop-shipment request within ten seconds after its support ticket is resolved.",
  "version": 1,
  "trigger": {
    "object": "ticket",
    "categories": [
      "shipping"
    ],
    "status": "resolved",
    "requiresAgentApproval": true
  },
  "identifiers": {
    "order": {
      "source": "ticket.orderRef",
      "required": true
    }
  },
  "conditions": [
    {
      "path": "shipment.status",
      "op": "eq",
      "value": "canceled",
      "id": "fulfillment_canceled",
      "description": "The provider confirms the referenced shipment is canceled",
      "applicableWhen": []
    }
  ],
  "instance": {
    "eventTypes": [
      "ticket.resolved"
    ],
    "initialRetrySeconds": 1,
    "maxRetrySeconds": 1,
    "maxAgeSeconds": 86400
  },
  "deadlineSeconds": 10,
  "severity": "high",
  "approved": true,
  "approvedAt": "2026-10-30T17:50:39.364Z",
  "enabled": true,
  "draftedBy": "template",
  "provenance": {
    "sources": [
      {
        "kind": "template",
        "ref": "Synthetic overdue provider acknowledgment example",
        "excerpt": "A queued shipment-stop request requires provider confirmation within ten seconds."
      }
    ],
    "assumptions": [
      "This synthetic provider acknowledgment has a ten-second deadline; it is separate from the two-minute refund rule."
    ]
  },
  "createdAt": "2026-10-30T17:50:39.364Z",
  "updatedAt": "2026-10-30T17:50:39.364Z"
}
Recorded outcomes (1)
Version and policy decision history

Rule versions

  • Version 1

    1 checks · 10 seconds · 54 min ago · 1 recorded executions

Policy decisions

No human policy decisions recorded. Approval alone is not retrofitted as acceptance.

Other rule actions