submit_payment_services_store_production_feed
submit_payment_services_store_production_feed is a Magento 2 cron job declared by the PaymentServicesSaasExport module in the Payment Services — Data Export group. It runs every minute (* * * * *) and dispatches Magento\PaymentServicesSaaSExport\Cron\StoreSubmitProductionFeed::execute() on every tick.
Wiring
- Group
- Payment Services — Data Export (payment_services_data_export)
- Module
- PaymentServicesSaasExport (magento/module-payment-services-saas-export)
- Schedule
- * * * * *
- Frequency
- every minute
- Handler
- Magento\PaymentServicesSaaSExport\Cron\StoreSubmitProductionFeed::execute()
- Source file
- vendor/magento/module-payment-services-saas-export/etc/crontab.xml
Run the submit_payment_services_store_production_feed cron job manually
Magento doesn't have a per-job CLI invocation — the smallest unit is a group. The command below runs every job in the payment_services_data_export group whose schedule is due. The --bootstrap flag bypasses the lock-file check so the job runs even when the system cron is configured.
php bin/magento cron:run --group=payment_services_data_export --bootstrap=standaloneProcessStarted=1Define your own job like this one
Want a job that fires on the same cadence in your own module? Drop these two files in — adjust the vendor/module namespace, the job name, and the body of execute.
1. etc/crontab.xml
<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Cron:etc/crontab.xsd">
<group id="payment_services_data_export">
<job name="vendor_module_submit_payment_services_store_production_feed_clone"
instance="Vendor\Module\Cron\SubmitPaymentServicesStoreProductionFeed"
method="execute">
<schedule>* * * * *</schedule>
</job>
</group>
</config>2. Cron handler class
<?php
declare(strict_types=1);
namespace Vendor\Module\Cron;
use Psr\Log\LoggerInterface;
class SubmitPaymentServicesStoreProductionFeed
{
public function __construct(
private readonly LoggerInterface $logger,
) {
}
public function execute(): void
{
$this->logger->info('submit_payment_services_store_production_feed cron tick');
// Your scheduled work here. Keep this short — long jobs
// should enqueue work onto the message queue rather than
// running inline in the cron tick.
}
}Need a full module scaffolded around this cron job? Module Generator wires the crontab.xml, handler class, and module registration for you.
Other cron jobs in PaymentServicesSaasExport
Sibling cron jobs declared by the same module. See all PaymentServicesSaasExport cron jobs →
submit_payment_services_order_production_feed
PaymentServicesSaasExport · every minute · * * * * *
submit_payment_services_order_sandbox_feed
PaymentServicesSaasExport · every minute · * * * * *
submit_payment_services_order_status_production_feed
PaymentServicesSaasExport · every minute · * * * * *
submit_payment_services_order_status_sandbox_feed
PaymentServicesSaasExport · every minute · * * * * *
submit_payment_services_store_sandbox_feed
PaymentServicesSaasExport · every minute · * * * * *
Cron handlers often dispatch Magento 2 events on each tick — observers bound to those events run as part of the scheduled work. The CLI Reference covers cron:run, cron:install, and the rest of the cron:* namespace.
Every Magento dev tool, in one hosted workspace.
Free to sign up. Nothing to install. Drafts, audits, and projects saved across every tool.