Pixie CRMHelp Centre
Sales & Marketing Hub · Feature guide

Set workflow execution hours and completion goals

Keep workflow actions within a chosen local-time window and stop a journey when its completion criteria are met.

Audience: authorised staffReviewed 13 November 2026

Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.

Where to start

Workflow → Open journey canvas → execution window and goal controls

Permission

Manage automation resources; independent Approve and Publish for revised workflow

Before you begin

Choose the time zone your team uses for this process. Stored run times are UTC, while the execution window is evaluated in the selected named time zone.

Follow these steps

  1. Enable the execution window and choose a valid IANA time zone.
  2. Select the permitted weekdays and a start/end hour on the same day. Use an end hour later than the start.
  3. Set the completion criteria. In the canvas, Stop when lifecycle reaches provides a simple lifecycle goal and preserves other existing goal criteria.
  4. Validate and rehearse the workflow, then save, review and publish the revised definition.
  5. Inspect a controlled run outside its window and another record that already meets the goal.

Fields and options

Window
Weekdays use Monday through Sunday. Start hours are 0–23; end hours are 1–24 and must be later than the start.
Completion criteria
Use supported profile conditions with All or Any matching. The goal is checked before each action.
Result
A run can wait for its next permitted window or finish as Goal reached without performing further actions.

Rules and limits

  • The window is a same-day range; a single overnight range is not supported.
  • An execution window does not change SMTP configuration or social-post scheduling.
  • A newly edited workflow does not rewrite the saved snapshot of an existing run.

Check the result

  • Check the stored time zone and next due time against a known local-time example.
  • Confirm a matching completion goal stops subsequent actions.

If something does not look right

  • If a run appears delayed, compare its due time, selected time zone and permitted weekday before resuming it.
  • If validation rejects hours, split the process rather than entering an overnight end hour earlier than the start.

Common questions

Can the window run from 22:00 to 06:00?

Not as one range. This release requires an end hour later than the start on the same day.

When is the goal checked?

Before each action, so a record that meets it can finish without receiving the remaining actions.