Recurring jobs
Learn how to set up recurring bulk edits that run automatically on a regular schedule using the Bulk Product Editor.
Overview
Recurring Jobs allow you to automate repetitive bulk editing tasks by setting them to run on a regular schedule. This is perfect for routine maintenance, regular price updates, inventory management, and ongoing content optimization.
Creating Recurring Jobs
Step 1: Configure Your Bulk Edit
- Set up filters to select target products
- Configure the modifications to be applied
- Test the configuration with a preview
- Ensure the job is suitable for recurring execution
Step 2: Set Recurrence Pattern
- Click "Create Recurring Job"
- Choose the recurrence frequency:
- Daily
- Weekly
- Monthly
- Custom interval
- Set the start date and time
- Optionally set an end date
Step 3: Configure Advanced Options
- Set timezone for execution
- Choose execution conditions
- Add job name and description
- Configure notifications
Recurrence Patterns
Daily Jobs
- Frequency: Every day, weekdays only, or custom days
- Use Cases: Inventory updates, price monitoring, content refresh
- Example: Daily inventory sync at 2 AM
Weekly Jobs
- Frequency: Specific days of the week
- Use Cases: Weekly sales updates, content rotation, collection updates
- Example: Every Monday at 6 AM - update featured products
Monthly Jobs
- Frequency: Specific date each month or relative dates
- Use Cases: Monthly pricing reviews, seasonal updates, report generation
- Example: First Monday of each month - review and update pricing
Custom Intervals
- Frequency: Every X days, weeks, or months
- Use Cases: Specialized business cycles, unique requirements
- Example: Every 14 days - rotate promotional content
Common Use Cases
Inventory Management
- Job: Daily low-stock alerts
- Schedule: Every day at 8 AM
- Action: Tag products with inventory < 10 as "low-stock"
Price Monitoring
- Job: Weekly competitive pricing
- Schedule: Every Sunday at midnight
- Action: Update prices based on market analysis
Content Rotation
- Job: Monthly featured products
- Schedule: First day of each month
- Action: Rotate products in "Featured" collection
SEO Maintenance
- Job: Weekly SEO optimization
- Schedule: Every Wednesday at 3 AM
- Action: Update missing meta descriptions
Seasonal Updates
- Job: Quarterly collection updates
- Schedule: First day of each quarter
- Action: Update seasonal tags and collections
Advanced Configuration
Execution Conditions
- Product Count Limits: Only run if X products match filters
- Change Detection: Only run if products have changed
- External Triggers: Integration with other systems
- Failure Handling: What to do if job fails
Smart Scheduling
- Load Balancing: Distribute execution across time periods
- Conflict Avoidance: Prevent overlapping jobs
- Priority Queuing: Handle multiple jobs efficiently
- Resource Management: Optimize system performance
Managing Recurring Jobs
Monitoring Active Jobs
- View all recurring jobs in the dashboard
- Check next execution times
- Review job history and performance
- Monitor success/failure rates
Modifying Recurring Jobs
- Select the job to modify
- Update schedule, filters, or modifications
- Choose whether to apply changes to future executions only
- Save the updated configuration
Pausing and Resuming
- Pause: Temporarily stop job execution
- Resume: Restart paused jobs
- Skip Next: Skip the next scheduled execution
- Force Run: Execute job immediately
Deleting Recurring Jobs
- Select the job to remove
- Choose whether to keep historical data
- Confirm deletion
- Job will stop executing immediately
Best Practices
Job Design
- Keep recurring jobs simple and focused
- Use stable filter criteria that won't become obsolete
- Test jobs thoroughly before setting them to recur
- Design jobs to be idempotent (safe to run multiple times)
Scheduling Strategy
- Avoid peak traffic times for execution
- Stagger multiple recurring jobs
- Consider business cycles and seasonal patterns
- Plan for holidays and special events
Monitoring and Maintenance
- Regularly review job performance
- Update jobs as business needs change
- Monitor for unexpected results
- Keep job documentation up to date
Performance Considerations
System Impact
- Large recurring jobs can affect system performance
- Schedule resource-intensive jobs during off-peak hours
- Consider breaking large jobs into smaller chunks
- Monitor execution times and optimize as needed
Data Consistency
- Ensure jobs don't conflict with each other
- Consider the order of execution for related jobs
- Plan for data dependencies
- Implement proper error handling
Examples
Example 1: Automated Inventory Management
Job Name: Daily Low Stock Alert
Schedule: Every day at 6 AM
Filters: Inventory ≤ 5 AND Status = Active
Action: Add tag "reorder-needed"
Notification: Email to inventory team
Example 2: Weekly Price Optimization
Job Name: Competitive Price Updates
Schedule: Every Sunday at 2 AM
Filters: Collection = "Electronics"
Action: Update prices based on template
Conditions: Only if competitor data available
Example 3: Monthly SEO Maintenance
Job Name: SEO Content Optimization
Schedule: First Monday of each month at 1 AM
Filters: SEO Title is empty OR SEO Description is empty
Action: Generate SEO content using templates
Notification: Report to marketing team
Troubleshooting
Common Issues
- Jobs not executing: Check schedule settings and system status
- Partial execution: Review filter criteria and product availability
- Performance problems: Optimize job scope and timing
- Unexpected results: Verify modification logic and test conditions
Recovery Procedures
- Implement rollback capabilities for critical jobs
- Keep audit trails of all changes
- Set up monitoring and alerting
- Plan for manual intervention when needed