5.4 Combining Agents with No-Code Workflows
SOURCE: 5.4 Combining Agents with No-Code Workflows
Unit 6: Testing, Ethics, and Scaling Automations
6a. Test and debug workflows and agents for accuracy and reliability.
6a.1. The Unit 6 reading on testing and debugging explains that you need to check both workflow steps and agent behavior so the automation does what you expect. To review, see: [6.1 Testing and Debugging Automations] DISCUSS: When you test a no-code automation or AI agent, which is more important for you first, finding logic errors or checking whether the output is accurate and reliable, and why?
To review, see:
[6.1 Testing and Debugging Automations]
SOURCE: [6.1 Testing and Debugging Automations]
6b. Apply ethical, privacy, and governance principles to AI automations.
6b.1. The Unit 6 reading on ethics and privacy asks you to think about how AI automations handle data, consent, and responsibility. To review, see: [6.2 Ethical and Privacy Considerations] DISCUSS: What ethical or privacy risk would matter most in an AI automation you might use, and what rule or control would you add to reduce that risk?
To review, see:
[6.2 Ethical and Privacy Considerations]
SOURCE: [6.2 Ethical and Privacy Considerations]
6c. Implement human oversight, approval steps, and error-handling mechanisms in automations.
6c.1. Unit 6 describes human oversight, approval steps, and error handling as ways to reduce risk when an automation makes a choice or meets a problem. These controls help you keep people involved when a workflow needs review or a backup plan. DISCUSS: When should an automation require human approval instead of acting on its own?
To review, see:
[6.3 Adding Human Oversight and Error Handling]
SOURCE: [6.3 Adding Human Oversight and Error Handling]
6d. Develop strategies to monitor, refine, document, and scale automations over time.
6d.1. Unit 6 presents monitoring, refinement, documentation, and scaling as ongoing parts of automation work, not one-time tasks. These practices help you support automations after launch and adapt them as needs change. DISCUSS: Which long-term practice is most important for keeping an automation useful over time, and why?
To review, see:
[6.4 Planning for Long-Term Use and Scaling]
SOURCE: [6.4 Planning for Long-Term Use and Scaling]

Last modified: Thursday, 18 June 2026, 1:29 PM
Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 94 of /mod/page/view.php: call to core\output\core_renderer->footer()