How Signal scheduling works

Each Signal runs automatically on a schedule you define. Understanding how scheduling and the lookback period interact will help you get the right amount of data at the right time.

Setting a schedule

During Signal creation (Step 4 of the wizard), you set three things:

• Frequency — how often the Signal should run (e.g., daily, weekly, bi-weekly or monthly)

• Time — what time of day to run it

• Timezone — which timezone the time refers to

💡 Tip: For most use cases, a daily schedule is the right choice — frequent enough to catch activity quickly, without running up unnecessary credits.

What the lookback period does

The lookback period tells the Signal how far back to search on its very first run. For example, if you set a 7-day lookback and your Signal runs for the first time on a Monday, it will collect relevant activity from the past 7 days.

After the first run, the lookback period no longer applies. Each subsequent run automatically picks up activity that occurred since the previous run — so you never miss anything and never see duplicates.

⚠️ Note: Setting a very long lookback period (e.g., 3 months) on the first run can collect a large volume of results and use more credits. Start with 7–14 days if you are unsure.

Changing the schedule later

You can update a Signal's schedule at any time by editing it — go to the actions menu (⋮) → Edit → navigate to the Schedule step. Changes take effect from the next run.

Viewing past runs

To see a log of when a Signal ran and what it found, go to the actions menu (⋮) next to the Signal and select Activity Logs. This shows each run's timestamp, how many results were collected, and any errors.

Schedule quick reference