Operations | Monitoring | ITSM | DevOps | Cloud

WooCommerce relies on a lot of work happening in the background. Some of that is handled by WordPress cron, while other tasks are queued through Action Scheduler. This can include things like sending scheduled emails, processing subscription renewals, delivering webhooks, running scheduled WooCommerce actions, and other maintenance tasks that do not happen during a normal page request. The problem is that when one of these background jobs stops running, it is not always obvious straight away.

A Rails migration is a timestamped Ruby class inheriting from ActiveRecord::Migration whose change method alters the database schema. bin/rails db:migrate runs each pending migration once, records its version in the schema_migrations table, and dumps the result to db/schema.rb. Rollbacks invert change; irreversible steps need up and down. On PostgreSQL and SQLite, each migration runs inside a transaction.