background-jobs

Designs, reviews, and diagnoses 1C:Enterprise background and scheduled jobs via Unica MCP tools.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill background-jobs-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: background-jobs
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/background-jobs
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill background-jobs-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Background and scheduled jobs in 1C:Enterprise often fail silently through duplicate launches, partial writes, stale locks, and unlogged retries. This Skill provides a structured workflow to design restartable jobs, review their failure behavior, and diagnose hangs or crashes using ЖР/ТЖ evidence. ## Core Features & Use Cases - Job design and review: Define execution contracts covering parameters, user context, transaction scope, idempotency keys, lock strategy, timeouts, retry counts, and structured logging fields. - Failure-mode analysis: Check duplicate launch, partial write, stale lock, external service failure, session termination, and crash-restart behavior before implementation. - Runtime diagnosis: Build timelines from ЖР/ТЖ logs and map the first failure back to module code using Unica MCP tools like unica.code.search, unica.meta.info, and unica.runtime.execute. - Use Case: A scheduled exchange job intermittently hangs in production. Use this Skill to locate the entry point, inspect lock and transaction behavior, and correlate ЖР/ТЖ events with the failing module. ## Quick Start Ask the assistant to review the scheduled job that synchronizes orders for restartability, locking, and retry safety using the background-jobs skill.

Frequently Asked Questions about background-jobs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a restartable background job in 1C:Enterprise?▼

Define an execution contract covering parameters, user context, transaction scope, idempotency key, lock strategy, timeout, retry count, and logging fields. Then verify failure behavior for duplicate launches, partial writes, stale locks, and crash restarts before implementation.

How to diagnose a hanging scheduled job in 1C?▼

Build a timeline from ЖР/ТЖ (event log and technological log) evidence and map the first failure back to the module code. Use unica.code.search to find entry points and unica.meta.info to inspect related metadata.

What logging fields should a 1C background job write?▼

Use structured logging with job id, parameters summary, correlation id, retry count, result, and sanitized error context. Never include secrets in job logs.

Can this skill execute runtime operations directly?▼

It routes execution through unica.runtime.execute: dryRun true previews the planned command without side effects, while dryRun false runs classified operations and returns terminal results. Unclassified operations are refused until a workspace is detected.

When should I use transactions-locks guidance instead of this skill?▼

When a job reads and then writes shared state, the transactions-locks reference governs lock handling so locks do not block unrelated users or tenants. This skill covers only job restartability and failure behavior.