The Scheduled Campaign automatically changes to passed. Is it correct behavior?
This behaviour is expected for the Scheduled type of campaign for sending the notifications. Once the notification has been sent, the status changes to Passed and the campaign becomes Inactive:
For Scheduled Campaigns, you may choose the date and time (accurately to seconds) to launch your campaign on that date. The notifications will appear for every customer at the specific time, making the campaign inactive after sending the notification. In case the campaign has already passed, the customers who signed up after that won't receive notification.
Related Articles
The feed is not generated by schedule, Cron Job status is "Missed". How to fix this?
The most common reason for the 'Missed' Cron jobs is that Cron is configured in such a way that the pauses between its runs exceed the Missed if Not Run Within time setting of the Cron jobs. For instance, Cron is scheduled to run at 1, 30, and 59 ...Does the extension provide the functionality to export orders automatically?
Yes, except for manual file download, the Export Orders module provides two options for automatic file export. Navigate to the Automatic Export tab on the profile configuration page (System > Export Orders > Profiles) to see the possible options: 1. ...I configured the extension to send emails but I don’t receive them according to the set schedule.
Please keep in mind that it takes 5-10 minutes for the cart to be considered abandoned, and only then, a campaign timer starts. Also, note that abandoned cart emails are being sent by Cron, and by default Cron sends emails once in 5 minutes. It means ...I installed the Abandoned Cart Email extension but emails are not sent.
The abandoned carts are tracked within the campaigns. To start sending emails to the customers, please create and configure a campaign in Marketing → Abandoned Cart Email → Campaigns. Here is our video guide for Abandoned Cart Email set up: Please ...I’ve enabled the extension but encountered the warning: Could not acquire lock for cron job: amasty_fpc_process_queue. How to resolve?
If the amasty_fpc_process_queue cronjob has Pending status, and you see this warning, it’s likely that the warming schedule needs to be adjusted. Such warnings generally occur when the extension tries to run the warming process when the previous one ...
Announcements
⚡ Have you enlarged the functionality of the Amasty extension with your own code? Share your improvements with us!
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket