daily
, larger is yearly
.placed
source order, which is considered the subscription's first run. In such case the subscription is marked as active
and the next run will be scheduled on current timestamp.activate_by_source_order
option as false
at creation time. In this case you are not limited to placed source orders (source order status isn't checked), but must define manually the starts_at
time (expires_at
time is optional). Also remember to use the _activate
attribute to activate the subscription, otherwise it will miss the next run._deactivate
and _cancel
attributes.place_target_order
option as false
at creation time if you prefer to place created orders manually.errors_count
counter is incremented, but the subscription is kept active
(unless expired
, deactivated
or cancelled
).succeeded_on_last_run
attribute to inspect subscription last run state: in case its value is false
, you can inspect the last associated order_copy
to fix any missing/bad data and manually place the copied order.webhooks
on order subscriptions and order copies events, to act promptly in case something unexpected happens.