Docs
Jobs
Dija responds in chat within seconds because longer tasks never block your conversation. Anything that calls connected tools, searches the web, or runs multiple steps becomes a job: a background task that logs every step and messages you when it finishes. You can keep chatting with Dija while jobs run.
How a job runs
Every job has a title, a goal, a step-by-step log, and usually a skill that defines the method for that task (see Skills and methods). When Dija starts a job, it states in one sentence what the job will do. For quick lookups, Dija waits roughly 10 seconds and answers directly in chat if the result is ready; otherwise, the result arrives once the job finishes.
Any external write, send, or delete proposed by a job passes through approvals like every other action (see Approvals and rules), and any job that reads your personal tools becomes private to you (see Private and shared work).
Checking status
- In chat: Ask
"What are you working on?"anytime. Dija knows every active team job, who requested it, and where it stands. If a teammate already ran the same lookup earlier, Dija shares that result right away and notes whose job produced it. - In the web app: Open Jobs in the Dija web app to switch between Under way and All jobs, showing each job's status, requester, subject, and cost. A workspace runs several jobs concurrently and queues additional ones automatically.
Each job shows one of eight statuses: Waiting to start, Working, Waiting for approval, Waiting for an answer, Paused, Done, Failed, or Cancelled. Opening a job shows who asked for it and its spend against its ceiling at the top, then its goal, current step, output, approval requests and its activity. Each line of the activity is one step with its time; Dija's own reads of a tool are dimmed, a run of the same step folds into one line, and a line with an arrow opens to show exactly what was read or sent.
Answering mid-job questions
When a job hits a decision only a person can make, it sends one clear question to your channel and changes status to Waiting for an answer. Reply directly in chat or type your answer on the job's view under Dija is waiting for your answer. If a job needs a tool category your team has not connected yet, it asks you to connect one and resumes automatically once the connection is live.
Questions route to whoever requested the job. For unprompted jobs triggered by external tool events, questions go to the teammate who owns that record, or to the workspace owner if no record owner is assigned.
Steering, pausing, and cancelling
- Steer mid-run: Tell Dija in chat (for example,
"Tell the research job to skip companies under ten people") or type in the Tell Dija what to do differently field on the job's view and click Send. The job applies your guidance on its next step. - Pause and resume: Click Pause to halt a job while preserving everything completed so far, and Resume to pick up where it stopped.
- Cancel: Click Cancel beside the job's status (or ask in chat) to stop it permanently. Its activity and already-executed external actions remain, while any pending approval requests are withdrawn.
The requester, the owner of the record being worked on, anyone above either of them, and the workspace owner can steer, pause, or cancel a job. Other teammates can read it unless the job is private.
Helper jobs
For multi-account or multi-step work, a parent job can delegate sub-tasks to helper jobs, each running its own skill and reporting a summary back to the parent. Helpers appear in the parent's log and on Jobs, and stop automatically if their parent fails or is cancelled.
Spend ceilings
Dija tracks every model call a job makes against your model's listed token rates. Under Settings, the workspace owner sets three Spend ceilings (monthly limits follow the calendar month in your company's timezone):
- Per job:
$5by default, shared across a parent job and all of its helpers. - Per person per month:
$200by default. Managers or the owner can set a custom Monthly limit for an individual on Team. - Per company per month:
$1,000by default.
Dija stops a job after the step that reaches its ceiling and notifies you; that step is already paid for, so a job can end slightly over. Reaching a monthly ceiling pauses model calls in chat and jobs until the limit is raised or the new month begins, and Dija says whether it is your limit or the company's and where it is raised: yours on Team, the company's in Settings. Model providers bill your company's API account directly (see Models and keys).
Receiving results
When a job completes, Dija sends a concise message with the job's title, outcome, any decisions or next steps, and a link to the full log. Results route to the channel you selected on You (or the channel you last wrote from; jobs started in a group channel post back to that group). Failed jobs explain why they stopped, while cancelled jobs send no result message.