A check-triggers-crypto run failed. This workflow is dispatch-only
— something fired it, which means the workers/trigger-gate/ Worker
judged a pending crypto trigger to be at or near its level. So this
is a failure on a run that had a REASON to run, not a routine tick.
A distinct identity from the daily check-triggers sweep on
purpose: the two share a script but not a cause, and the repo
already learned with fetch-ohlcv's two modes that one title for two
causes lets a success on one close the other's issue.
Degradation: the affected orders are picked up by the daily 13:00
UTC sweep, which evaluates every asset class.
Detected by this run.
A
check-triggers-cryptorun failed. This workflow is dispatch-only— something fired it, which means the
workers/trigger-gate/Workerjudged a pending crypto trigger to be at or near its level. So this
is a failure on a run that had a REASON to run, not a routine tick.
A distinct identity from the daily
check-triggerssweep onpurpose: the two share a script but not a cause, and the repo
already learned with fetch-ohlcv's two modes that one title for two
causes lets a success on one close the other's issue.
Degradation: the affected orders are picked up by the daily 13:00
UTC sweep, which evaluates every asset class.
Detected by this run.