JODA
Create, pause, run, and troubleshoot a JODA Automation
Build a safe manual, scheduled, or event-triggered AI run and use history to understand its result. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.
Before you begin
- Audience: Standard user with JODA Automation access, manager, company admin.
- JODA access
- valid trigger/action
- recipients and event scope where needed
- permission to records/actions at run time
- approval for automation creation/update if staged through JODA.
JODA App → left rail Automations (Beta)
Create, pause, run, and troubleshoot a JODA Automation
-
Open the workspace
In JobBuddy, go to JODA App → left rail Automations (Beta).
-
Confirm access and starting state
JODA access; valid trigger/action; recipients and event scope where needed; permission to records/actions at run time; approval for automation creation/update if staged through JODA.
-
Complete the main setup
Review templates and New automation Basics/Trigger/Action tabs Active/Paused/Disabled/Completed
-
Review the important choices
schedule/event/manual triggers time zone and cron/interval guidance conversation versus notification output and recipients
-
Check status and follow-up
Run now, Pause/Resume, Stop, Edit, Delete, History, view conversation, last error, and permissions at execution time. Warn that a background run should not be used for unsupervised destructive work.
-
Verify the result
Build a safe manual, scheduled, or event-triggered AI run and use history to understand its result.
Expected result: Build a safe manual, scheduled, or event-triggered AI run and use history to understand its result.
Troubleshooting
The page, control, or action is unavailable.
Confirm the required access and starting state: JODA access; valid trigger/action; recipients and event scope where needed; permission to records/actions at run time; approval for automation creation/update if staged through JODA.
The result is incomplete or unexpected.
Trigger type, one-time/cron/interval schedule, time zone, event scope, conversation versus notification execution, recipients, reuse mode, status, manual run, errors, and target-record permissions make this a high-risk background workflow.
The issue remains after checking the record.
Capture the exact visible error, record status, approximate time, and intended result. Give support only the minimum customer-safe evidence needed to trace the problem.
What happens next
- Build a safe manual, scheduled, or event-triggered AI run and use history to understand its result.
- Review the resulting record, status, notifications, and related history before continuing downstream work.
- Use the related guide when the next action belongs to another JobBuddy workflow.