# How to control workflowID in Temporal Schedule

**URL:** <https://community.temporal.io/t/how-to-control-workflowid-in-temporal-schedule/12923>\
**Category:** Community Support\
**Tags:** cron\
**Created:** [July 23, 2024, 7:58am UTC](https://community.temporal.io/t/how-to-control-workflowid-in-temporal-schedule/12923 "2024-07-23T07:58:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thienha](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/thienha/32/5613_2.png) [@thienha](https://community.temporal.io/u/thienha)\
**Post date:** [July 23, 2024, 7:58am UTC](https://community.temporal.io/t/how-to-control-workflowid-in-temporal-schedule/12923/1 "2024-07-23T07:58:07Z")

</div>

When the workflow is trigger by schedule, the workflow ID is appended with the timestamp for the run. How to avoid any prefix/suffix appended, just purely what ever I set?

````auto
ScheduleActionStartWorkflow(
                        ...,
                        ...,
                        id=my_unique_id,
                        task_queue=...,
                    ),```

This breaks the uniqueness constraint that I'm trying to use that workflow Id is offering.
````

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [July 25, 2024, 1:54pm UTC](https://community.temporal.io/t/how-to-control-workflowid-in-temporal-schedule/12923/2 "2024-07-25T13:54:36Z")

</div>

Hi @thienha

That is the current implementation, we have an open issue to make it more flexible [Schedules - add option for execution workflowid to be "as-is" (not unique per run) · Issue #4795 · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/issues/4795)

Please feel free to comment on it.

Antonio