주제: Operations

홈으로

  • Minute Triggers in GAS: Runtime Budgets and Overlap Prevention

    한국어로 읽기 TECH INSIGHT / EXPLAINED A 54-second loop inside a minute trigger can look almost continuous. Its practical constraints are daily runtime and overlapping executions, more than the six-minute per-run limit. Decide the required observation frequency before filling the available time.

  • Split Telegram Alerts: Authenticate Recipients and Track Delivery

    한국어로 읽기 TECH INSIGHT / EXPLAINED Users need to know what happened to an order; operators need to know why. Creating two messages from one event reduces noise. Splitting channels alone, however, does not establish privacy isolation.

  • Home PC or VPS: Define Recovery Requirements Before Comparing Cost

    한국어로 읽기 TECH INSIGHT / EXPLAINED Before comparing a home PC with a VPS, write down the acceptable outage duration. A job that can resume tomorrow and a bot that must reconcile open orders need different hosting decisions.

  • Diagnosing a Stalled Bot: Process, Progress and Feed Freshness

    한국어로 읽기 TECH INSIGHT / EXPLAINED A frozen dashboard does not identify the failed component. First distinguish an exited process, a live process without progress, an intentional idle state and a display that stopped updating while the bot continued.

  • Running a Trading Bot 24/7 on Windows: Restarts, State, and Health

    한국어로 읽기 TECH INSIGHT / EXPLAINED A bot that stays running and a bot that safely resumes trading are different operational states. On Windows, plan for reboot, sleep, failed upgrades and uncertain orders before relying on automatic restarts. Running all day does not mean trading outside the market’s supported session.