Fast answer
Kraken signal checks begin with the order instruction.
Before treating a Kraken-related signal as useful, check whether the provider clearly names the pair, market, order type, trigger condition, stop or conditional close, and result label. A venue name does not verify the provider's call.
If the alert does not say how the order should behave, treat it as incomplete.
Order checks
What to inspect in a Kraken signal.
Order type
Market, limit, stop-loss, target, trailing, and conditional-close language should be clear before the trade.
Pair and platform
The provider should name the asset pair and whether the alert assumes Kraken Pro, spot, margin, or futures context.
Timing and edits
Check original timestamps, edited messages, canceled orders, missed entries, and whether later changes are preserved.
Final status
A complete record labels filled, missed, canceled, stopped, partially closed, and still-open calls.
Official context
Kraken supports multiple order-type paths.
Kraken's order-type support lists market, limit, stop loss, target, trailing, iceberg, conditional close, and related order options. That variety is useful only when a provider records exactly which instruction was sent.
Review standard
Review the provider record, not the exchange label.
A reviewable Kraken signal includes original alert text, pair, order type, trigger, entry window, stop or invalidation, update trail, final status, and notes for any order that did not fill.