Skip to main content
External indicators expire after 24 hours. To keep your signals visible, you need to continuously update them.

Update Strategies

Cron Job

Simple scheduled task that runs at intervals

Webhook

Trigger updates based on events

Always-On Service

Long-running process with internal scheduler

Serverless

AWS Lambda, Google Cloud Functions, etc.

Option 1: Cron Job (Linux/Mac)

The simplest approach for servers with cron support.

Setup

  1. Create your indicator script:
  1. Add to crontab:

Option 2: Python Scheduler

For more control, use Python’s schedule library:
Run with:

Option 3: Node.js with node-cron

Option 4: Docker Container

Create a containerized indicator service:
Deploy:

Option 5: AWS Lambda (Serverless)

handler.py

CloudWatch Event Rule

Option 6: GitHub Actions

Free CI/CD with GitHub:
GitHub Actions has a 5-minute minimum interval for scheduled workflows, and jobs may be delayed during high load periods.

Monitoring & Alerts

Logging Best Practices

Health Check Endpoint

If running as a service, add a health check:

Slack/Discord Alerts

1

Development

Manual runs with python update_signals.py
2

Testing

Local scheduler with schedule library
3

Production

Docker container or cloud service (Lambda/Cloud Functions)
4

Monitoring

Add logging, health checks, and alerts

Frequency Guidelines

For most strategies, updating at bar close is sufficient. This reduces API calls and ensures signals are based on complete bars.

Next Steps

Signal Best Practices

Improve signal quality

API Reference

Complete API documentation