-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unabling real time processing makes the workflow unactive - Moodle 4.0+ #193
Comments
Hello, I'm experiencing the same issue with Moodle 4, if Real time processing is unchecked / disabled then the workflow does not work. Is this a bug? Thanks |
hi all, eventually we are hoping to deprecate this plugin in favor of a way more flexible and power one called dataflows: https://github.com/catalyst/moodle-tool_dataflows Data flows is ready right now, but it cannot currently be triggered from an event, but this is on the road map: catalyst/moodle-tool_dataflows#31 So please check out data flows and see what you think and if anyone is interested in sponsoring the event trigger please let us now |
hi @brendanheywood, does your answer mean that there will be no attempt from your side (meaning Catalyst) to fix this issue? Is event trigger abandoned project as of now? Thanks! |
hi @FurloSK The event trigger step in tool_dataflows is now implemented and we are using in prod for a couple clients. If you are creating something new I'd definitely recommend you create it using dataflows instead of tool_trigger. If you have an existing tool_trigger setup then there should be no reason to stop using something is working, but I would also encourage you to take a look at dataflows you may find rebuilding it using that is not really that much work and gives you a lot of other side benefits. We still have clients using tool_trigger in prod, but we are not expecting any new clients to start using it. So I would characterize this plugin as deprecated rather than abandoned. If you really want this issue fixed, we'd welcome a pull request, or if you want to sponsor it we could look at that as well, but I still think your best bet is to use dataflows instead. |
hi @brendanheywood,
|
hi @FurloSK
|
This is a very quick list of concepts to get started: |
When testing the plugin and deactivating the Real Time Processing option, the steps of the current workflow never executes.
I have configured a server that can receive some HTTP POST Actions, but this only works when the previous option is enabled. Even if this works correctly when it's enabled, I don't want the end user to see the error on their Moodle page, just in the logs that the plugin manages on each workflow history.
These are my current settings for the plugin
Moodle version: 4.0.1
The text was updated successfully, but these errors were encountered: