Running a stream manually

How to trigger a stream on demand from the Control Panel, what a manual run does differently from a scheduled or webhook run, and when to use it.

You can trigger a stream on demand from the Control Panel, rather than waiting for its schedule or for a webhook to arrive. This is a manual run.

When to use a manual run

  • Testing a stream straight after a mapping or configuration change, before waiting for the next scheduled run.

  • Catching up a backlog, for example after a stream has been paused or a destination was unavailable.

  • Reprocessing a specific window of data, such as a particular date range, without waiting for the schedule to reach it.

For routine day-to-day syncing you do not need to trigger runs yourself: streams already run on a schedule or in response to a webhook. See The Jobs page for how scheduled, webhook and manual runs each create a job.

How to trigger a manual run

  1. In the Control Panel, open the stream you want to run.

  2. Use the manual run action on the stream's page to trigger it.

  3. If a settings popup appears, enter any run-specific options it asks for, such as a date range to reprocess. Leave these blank to run with the stream's normal settings.

  4. Confirm the run.

The run is queued and starts as soon as capacity allows, rather than immediately. It creates a job like any other run, so you can follow its progress, see how many events it created, and check for failures from the Jobs page.

Manual, scheduled and webhook runs

A stream can be triggered three ways, and all three create the same kind of job:

  • Scheduled: the stream runs automatically on its configured schedule, for example every 15 minutes.

  • Webhook: a connected system pushes data to HC as it happens, which starts a job to process it.

  • Manual: you trigger the run yourself from the Control Panel.

A manual run does not change the stream's schedule or disable future scheduled runs: it simply runs the stream once, immediately, in addition to its normal triggers.

Before you run one

A manual run reprocesses data, so if you are unsure whether it could create duplicate records in your destination system, check with HC first. Entity deduplication protects against most repeat records, but it is worth confirming for financial data. If you only need to rerun a single previous run rather than trigger a new one, use Replicate on that job instead — see The Jobs page.