# Would "updateWithStart" make sense?

**URL:** <https://community.temporal.io/t/would-updatewithstart-make-sense/10444>\
**Category:** Community Support\
**Tags:** general-impl, typescript-sdk\
**Created:** [December 23, 2023, 10:05pm UTC](https://community.temporal.io/t/would-updatewithstart-make-sense/10444 "2023-12-23T22:05:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bnpnt](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/bnpnt/32/3689_2.png) [@bnpnt](https://community.temporal.io/u/bnpnt)\
**Post date:** [December 23, 2023, 10:05pm UTC](https://community.temporal.io/t/would-updatewithstart-make-sense/10444/1 "2023-12-23T22:05:38Z")

</div>

Now that Workflow Updates are landing in TS SDK (and Core!), I was thinking about supporting `updateWithStart`.

I’m thinking specifically about TS SDK since it’s the one I use the most but I’d say other SDKs would follow the same idea.

The client calls `updateWithStart` for a given workflow ID and, if one is running, it registers the update. If not, it starts the workflow with that given update request, and waits for the update to return.

So, basically the same idea behind `signalWithStart`. I can think of some use cases, e.g. a workflow that processes transactions for a given key serially. One could model this as a long running workflow, where each transaction is an update to a workflow with the key as the workflow id.

If you don’t have `updateWithStart`, you’d have to either check if the workflow is running and call `startUpdate` (or `executeUpdate`) or start the workflow and then call `start/executeUpdate`, which implies two round trips to the Temporal Server instead of one.

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [December 24, 2023, 9:44pm UTC](https://community.temporal.io/t/would-updatewithstart-make-sense/10444/2 "2023-12-24T21:44:15Z")

</div>

Yes, we are planning to implement `UpdateWithStart `with a semantic similar to `SignalWithStart`.

---

<div class="post-metadata">

**Author:** ![frko](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/frko/32/4160_2.png) [@frko](https://community.temporal.io/u/frko)\
**Post date:** [August 21, 2024, 12:03pm UTC](https://community.temporal.io/t/would-updatewithstart-make-sense/10444/3 "2024-08-21T12:03:53Z")

</div>

Hi @maxim is there a beta or rc available for us to test with?

---

<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:** [August 22, 2024, 2:02pm UTC](https://community.temporal.io/t/would-updatewithstart-make-sense/10444/4 "2024-08-22T14:02:08Z")

</div>

Hi @frko

Development is in progress, but we don’t have an ETA yet

Antonio

---

<div class="post-metadata">

**Author:** ![drewhoskins-temporal](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@drewhoskins-temporal](https://community.temporal.io/u/drewhoskins-temporal)\
**Post date:** [September 26, 2024, 11:18pm UTC](https://community.temporal.io/t/would-updatewithstart-make-sense/10444/5 "2024-09-26T23:18:44Z")

</div>

Update-with-start is out in pre-release for Go users and, any day now, Java.  
Typescript support is a priority, though we don’t have a date to announce at this time.