'cron' 검색 결과

Background orchestrator that drains the system-wide cron-actions-queue.jsonl queue safely, preventing LLM context pollution in the primary router.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Schedule a prompt to run later, once or on a repeating cron expression.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work with the @upstash/qstash TypeScript/JavaScript SDK, an HTTP-based message queue, task scheduler, and background job system for serverless and edge runtimes (Next.js, Vercel, Cloudflare Workers, Deno, Node.js). Use when publishing messages to HTTP endpoints or URL groups, running background jobs without a long-running worker process, scheduling with cron expressions, delaying messages, building FIFO queues with parallelism and flow control, configuring retries and callbacks, handling a dead letter queue (DLQ), deduplicating messages, fanning out to multiple endpoints, verifying QStash webhook signatures (Next.js App Router, Pages Router, and Edge Runtime), running a local QStash dev server, or migrating regions. Also use when the user asks for a serverless cron job, async task queue, job scheduler, delayed delivery, webhook delivery with retries, or event-driven messaging between services.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure failures — e.g., webhook handlers that drop events, flaky cron jobs, background jobs that fail mid-execution, or workflows that need to resume where they left off. Covers Inngest function configuration, triggers (events, cron, invoke), step execution and memoization, idempotency, cancellation, error handling, retries, logging, and observability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scheduled jobs on PaaS and in the cloud — cron syntax, reliability, and observability — vendor-neutral patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read, write, and debug cron expressions with field reference, scheduling logic, and common patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when adding, reviewing, or repairing Pharos Worker cron schedules, slot dispatch, leases, or runtime experiments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Opinionated house conventions for NestJS backends — module boundaries and layering, provider wiring and injection scopes, guards/interceptors/pipes/filters, DTOs and validation, domain exceptions, config, and the Nest 11 / Express 5 behaviour that compiles cleanly and fails at runtime. Use whenever the code is NestJS (`@nestjs/*` in package.json, or `@Module`/`@Injectable`/`@Controller`/`@Cron` in the file), including when the question sounds like plain TypeScript, an OOP refactor, a code review, or an ops problem — the Nest-specific answer differs from the generic one. Typical asks: scaffolding a module, adding a controller, provider, or endpoint, wiring an enhancer, a boot-time DI or circular-import failure, a response leaking entity fields despite `@Exclude()`, a cron job firing on every replica, upgrading NestJS, or reviewing a Nest diff. Not for plain Express or Fastify, Angular, frontend, SQL, or CI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, configure, debug, and optimize OpenClaw AI agent deployments. Master guide for gateway configuration, openclaw.json settings, model routing and fallback chains, skills development and publishing, cron job scheduling, memory systems (Qdrant, Neo4j, SQLite), Docker infrastructure, and Tailscale VPN networking. Includes config analyzer that audits your openclaw.json and suggests improvements, plus health checker that validates all OpenClaw subsystems. Built for AI agents — Python stdlib only, no dependencies. Use for OpenClaw setup, gateway debugging, skill building, cron management, model optimization, cost reduction, and infrastructure troubleshooting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a Codex prompt on a cron schedule or at a specific future time. Codex app Automations is the official, always-on surface for durable recurring schedules — recommend it FIRST; this local skill is a terminal fallback that only fires while its daemon runs. Triggers include "/schedule", "cron", "every Monday 9am", "run this at 3pm", "schedule a codex prompt", "recurring codex task", and one-time future runs ("run once at 3pm", "remind me to check X tomorrow"). For fixed-interval repeats ("every N minutes"), use the separate `loop` skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose Hermes cron jobs that ran successfully at scheduler level but produced empty, missing, or non-actionable user output.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose and safely document Hermes cron script interpreter mismatches, especially when shell scripts are executed as Python or Python wrappers are executed as shell.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add recurring scheduled jobs (crons) to the Convex app.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add recurring scheduled jobs (crons) to the Convex app.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Selbstjustierende Takt-Regelschleife für wiederkehrende Agenten-Scans. Nutzen, wenn ein geplanter Scan sein Intervall bei Aktivität schärfen und bei Stille abkühlen soll, ohne Operator-Eingriff.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use WooCommerce's customer and session APIs correctly — WC ships its own session handler (WC_Session_Handler, single wp_woocommerce_sessions table for both guests and logged-in users) and its own customer object (WC_Customer via WC()->customer), separate from $_SESSION / native PHP sessions / wp_get_current_user. AI consistently reaches for $_SESSION (breaks with page caching, setcookie (no signing, no namespacing), or user_meta for guests (impossible). The correct path is WC()->session->set/get for ephemeral per-visitor data, WC()->customer->get_billing_* for the active customer context including guests, and new WC_Customer($user_id) for one-off loads. Important — WC()->session is auto-initialized only on frontend requests (incl. admin-ajax); REST, cron, and WP-CLI must call wc_load_cart() explicitly. Use when storing per-visitor state, reading the current visitor's billing data, or debugging session loss across page caches / REST / cron. Triggers on WC_Session, WC_Session_Handler,...

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and review Action Scheduler jobs in WordPress plugins using Action Scheduler 3.9.x public APIs - async, single, recurring, and cron-expression actions; action_scheduler_init load timing; hook/args/group naming; unique and priority parameters; idempotent callbacks; chunked workloads; activation/deactivation cleanup; WooCommerce-bundled or standalone dependency usage; admin and WP-CLI debugging; queue runner limits; and safe operational troubleshooting. Use when a plugin schedules background jobs with as_enqueue_async_action, as_schedule_single_action, as_schedule_recurring_action, as_schedule_cron_action, as_get_scheduled_actions, or integrates with WooCommerce background queues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate docs from live git+skills+cron state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating or editing cron jobs - prevents timeouts, silent failures, and delivery gaps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for environment validation: .env, config.yaml, paths, Python, Git — check + auto-fix + cron every 60min.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Argo Workflows — argo Workflows management for Kubernetes-native workflow orchestration. Covers workflow templates, cron workflow scheduling, artifact management, workflow execution, parameter handling, and resource monitoring. Use when checking workflow status, investigating step failures, managing templates, or auditing cron workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.