ActionScheduler_HybridStore::mark_complete()
Method: Mark an existing action complete whether migrated or not.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:326
Method: Mark an existing action complete whether migrated or not.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:326
Method: Mark an existing action as failed whether migrated or not.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:302
Method: Migrate a list of actions to the table data store.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:229
Method: Find actions matching the query in the secondary source first.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:162
Method: Release a claim in the table data store.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:405
Method: Save an action to the primary store.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:241
Method: When the actions table is created, set its autoincrement value to be one higher than the posts table to ensure that there are no ID collisions.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:73
Method: Store the demarkation id in WP options.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:120
Method: If any actions would have been claimed by the secondary store, migrate them immediately, then ask the primary store for the canonical claim.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:211
Method: Release claims on an action in the table data store.
Source: packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php:414