New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[STU-74] Triggering an event after a successful refresh on queue jobs? #283
Comments
@sunscreem Are you triggering a full import using the CLI command? |
Hey @janhenckens - coincidentally I managed to sort this just last night. The issue was that supervisor needed restarted to pick up my changed code, only I hadn't notice it wasn't doing so in my deployments due to a permissions issue. This is working a treat now. I use it alongside Oh Dear - Health Check to make sure my indexes are updating on a cron job overnight. Although not needed, an event such as |
Good to hear you got it working! Not having to check it for every queue job is probably a lot more efficient on your end, I'll put it on the list and let you know when it's available :) |
Awesome! |
Had to work on some other issues for the plugin so rolled this in already :) It's out in 3.3.1, you can find documentation here |
@janhenckens Works perfectly. Thank you! |
I'm wondering if anyone has worked out how to trigger an event when an update of the indexes has successfully completed.
The complication is I'm using supervisor to run my queue, so on my local testing this works great... But it doesn't seem to fire in production, I'm guessing because of how Craft runs queue jobs using supervisor?
Essentially what I'm trying to do is update a timestamp the last time a cron job to update my scout index is successfully completed.
STU-74
The text was updated successfully, but these errors were encountered: