| name | background-jobs |
| description | Фоновые и регламентные задания 1С. Используй когда нужно спроектировать, проверить или диагностировать background jobs, расписания, очереди, зависания, retry-логику и журналирование. |
Background Jobs
MCP routing
- Preferred path: use MCP
unica tools unica.project.map, unica.code.search, unica.meta.info, unica.code.diagnostics, unica.standards.search, unica.standards.explain, and unica.runtime.execute.
- Use
unica.role.info 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, locks, and security boundaries.
- Read
references/platform/runtime-diagnostics.md when the task includes ЖР/ТЖ, hangs, retries, or process/session evidence.
Workflow
- Identify job type: scheduled job, background job launched from code, queue worker, exchange worker, or deferred integration retry.
- Find entry points with
unica.code.search; inspect related metadata with unica.meta.info and project layout with unica.project.map.
- Define execution contract: parameters, user context, transaction scope, idempotency key, lock strategy, timeout, retry count, and logging fields.
- Check failure behavior before implementation: duplicate launch, partial write, stale lock, external service failure, session termination, and restart after crash.
- Run
unica.code.diagnostics and unica.runtime.execute for syntax/tests/launch verification when the project runtime is available.
- 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.
- Managed locks protect shared state without blocking unrelated users or tenants;
follow a stable lock order before reading and writing shared registers.
- 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.
