> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trinigence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trading Schedules

> How trading schedules work in Trinigence, when to use them, and how to avoid common mistakes.

## What a trading schedule is

A trading schedule defines **when a strategy is allowed to open new trades**.

Schedules are a risk and behavior control layer:

* reduce exposure during unwanted periods
* keep behavior consistent with your intent
* prevent trades in low-liquidity or high-risk windows

By default, schedules usually affect **entries**, not exits.

<Info>
  Schedules are filters, not signals.
</Info>

***

## Common schedule types

### Day-of-week schedules

Examples:

```text theme={null}
Trade only on Monday, Wednesday, Thursday, and Friday.
Do not trade on weekends.
```

Use cases:

* avoid weekend volatility in crypto
* match your preferred monitoring days
* remove periods with historically weak performance

***

### Time-of-day schedules

Examples:

```text theme={null}
Only trade between 08:00 and 20:00 UTC.
Do not open trades after 22:00 UTC.
```

Use cases:

* avoid low-liquidity hours
* exclude high-slippage windows
* align with your workflow

***

### Session-based schedules

Examples:

```text theme={null}
Trade only during London and New York sessions.
Avoid the Asian session.
```

Use cases:

* focus on high-liquidity sessions
* reduce noise during off-hours
* better match volatility expectations

<Warning>
  Sessions are timezone-sensitive. Always specify timezone when sessions matter.
</Warning>

***

## What schedules affect

In most strategies, schedules control:

* whether entry logic is evaluated
* whether a new position can be opened

Typically schedules do **not**:

* close open trades automatically
* override exit logic

If you want “close at a certain time,” you must define it as an exit rule.

<Card title="Time & session logic" icon="calendar-clock" href="/indicators-logic/time-and-session-logic" horizontal>
  Learn the difference between filters and triggers.
</Card>

***

## Timezone behavior

Schedules depend on timezone.

If timezone is:

* explicitly defined → schedule is evaluated in that timezone
* missing → Trinigence uses a safe default and shows it

Best practice:

* use UTC for consistency unless you have a reason not to

***

## Combining schedules with filters

Schedules are commonly combined with indicator filters.

Example:

```text theme={null}
Trade only during London session AND only when the 4h trend is bullish.
```

This typically:

* reduces trade frequency
* reduces exposure
* improves selectivity

But it can also reduce trade count too far if overdone.

***

## Defaults and assumptions

If schedule is:

* explicit → applied exactly
* implied (“weekdays only”) → inferred conservatively
* ambiguous → ATI asks for clarification

<Card title="What Trinigence fills automatically" icon="robot" href="/writing-ideas/what-trinigence-fills-automatically" horizontal>
  See how schedule gaps are handled.
</Card>

***

## Common mistakes

<AccordionGroup>
  <Accordion title="Assuming schedule closes open trades">
    Schedules restrict entries. Exits must be defined separately.
  </Accordion>

  <Accordion title="Over-restricting trading windows">
    Narrow schedules can eliminate trades and create misleading backtests.
  </Accordion>

  <Accordion title="Ignoring timezone shifts">
    Session rules can shift by an hour depending on timezone assumptions.
  </Accordion>

  <Accordion title="Using schedule to fix a bad strategy">
    Schedules improve behavior, but they don't create edge.
  </Accordion>
</AccordionGroup>

***

## Best practices

* Start with simple rules (weekdays only)
* Use UTC when possible
* Avoid over-restricting early
* Validate trade count after adding schedules
* If you need “close at time,” define an explicit exit

<Card title="Schedule & filters" icon="calendar-days" href="/strategy-structure/schedule-and-filters" horizontal>
  See how schedules fit into strategy structure.
</Card>

***

## What to read next

<CardGroup cols={2}>
  <Card title="Trade frequency & exposure" icon="clock-rotate-left" href="/risk-execution/trade-frequency-and-exposure">
    Schedules directly change frequency.
  </Card>

  <Card title="How to read results" icon="magnifying-glass-chart" href="/backtesting/how-to-read-results">
    Check trade count after scheduling.
  </Card>

  <Card title="Common pitfalls" icon="triangle-exclamation" href="/backtesting/common-pitfalls">
    Scheduling mistakes that mislead.
  </Card>

  <Card title="Time & session logic" icon="calendar-clock" href="/indicators-logic/time-and-session-logic">
    Time-based conditions in detail.
  </Card>
</CardGroup>

<Note>
  Schedules reduce opportunity.\
  Use them to reduce risk - not to force profitability.
</Note>