Background Jobs

Background Jobs

MCP routing

• Preferred path: use MCP unica tools unica.view {}, unica.search, unica.view on the object node, unica.check, unica.docs, and unica.run.
• Runtime идёт через unica.run: вызов без op отдаёт словарь операций и контракт каждой — argsSchema, execution, previewRequired, ifRevRequiredOnApply. Контракт вызова бери оттуда, а не из этого текста; выбирай только операцию с implemented: true и не выдумывай аргументов записи с argsSchema: null; превью исполнением не является. Не обходи контракт прямым runner-ом.
• Use unica.view on the role node when job behavior depends on user context or permissions.
• Do not call internal runtime, analyzer, standards, or package adapters directly. They are hidden behind MCP unica.

References

• Read ../../references/platform/platform-mechanics.md for background job context, temporary storage, and security boundaries.
• Read ../../references/platform/transactions-locks.md when the job reads and then writes shared state; this skill keeps only job restartability.
• Read ../../references/platform/runtime-diagnostics.md when the task includes ЖР/ТЖ, hangs, retries, or process/session evidence.

Workflow

1. Identify job type: scheduled job, background job launched from code, queue worker, exchange worker, or deferred integration retry.
2. Find entry points with unica.search; inspect related metadata with unica.view on the object node and project layout with unica.view {}.
3. Define execution contract: parameters, user context, transaction scope, idempotency key, lock strategy, timeout, retry count, and logging fields.
4. Check failure behavior before implementation: duplicate launch, partial write, stale lock, external service failure, session termination, and restart after crash.
5. Run unica.check on the module node; launch a client through unica.run (client.run) when the diagnosis needs one, and record runtime verification as unavailable unless separate evidence is supplied: test runs are outside the v0.13 surface.
6. For diagnosis, build a timeline from ЖР/ТЖ and map the first failure back to module code.

Review checklist

• Job can be safely restarted or retried.
• Long work is split or checkpointed.
• Logs use structured logging fields: job id, parameters summary, correlation id, retry count, result, and sanitized error context, but no secrets.
• Shared state a job reads and then writes is handled per transactions-locks, and the lock does not block unrelated users or tenants.
• Failure paths distinguish retryable and permanent errors.

Contract gaps

If public MCP unica cannot inspect schedules, active jobs, lock state, or runtime artifacts needed for the task, report a Unica MCP contract gap with the missing operation.