JODA
Fix a missing, wrong-scope, failed, or stuck JODA result
Diagnose context, source, permission, validation, approval, or automation-run failures without repeating unsafe actions. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.
Before you begin
- Audience: Standard user, manager, company admin.
- Exact conversation/run, source record, error text, approximate time, and intended result
- permission to inspect source/history.
JODA conversation; JODA App conversation history/Automations history; source record; Inbox workflow error where emitted
Fix a missing, wrong-scope, failed, or stuck JODA result
-
Open the workspace
In JobBuddy, go to JODA conversation; JODA App conversation history/Automations history; source record; Inbox workflow error where emitted.
-
Confirm access and starting state
Exact conversation/run, source record, error text, approximate time, and intended result; permission to inspect source/history.
-
Complete the main setup
Check in this order: confirm project/record/source → permissions/module/status → file processing → required fields/validation → live approval state → automation trigger/run history → external service.
-
Review the important choices
Review starting a focused new conversation versus continuing, refreshing/reopening, not re-approving stale cards, viewing run conversation/errors, and what evidence to give support without customer-sensitive data.
-
Verify the result
Diagnose context, source, permission, validation, approval, or automation-run failures without repeating unsafe actions.
Expected result: Diagnose context, source, permission, validation, approval, or automation-run failures without repeating unsafe actions.
Troubleshooting
The page, control, or action is unavailable.
Confirm the required access and starting state: Exact conversation/run, source record, error text, approximate time, and intended result; permission to inspect source/history.
The result is incomplete or unexpected.
Wrong project/source, missing access, incomplete structured fields, processing, context drift, stale approval, tool/service failure, provider limits, and background-run errors can look similar in the final message.
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
- Diagnose context, source, permission, validation, approval, or automation-run failures without repeating unsafe actions.
- 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.