# How to update workflow memo in Typescript?

**URL:** <https://community.temporal.io/t/how-to-update-workflow-memo-in-typescript/9583>\
**Category:** Community Support\
**Tags:** typescript-sdk\
**Created:** [September 23, 2023, 6:27pm UTC](https://community.temporal.io/t/how-to-update-workflow-memo-in-typescript/9583 "2023-09-23T18:27:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethanjdiamond](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ethanjdiamond/32/4339_2.png) [@ethanjdiamond](https://community.temporal.io/u/ethanjdiamond)\
**Post date:** [September 23, 2023, 6:27pm UTC](https://community.temporal.io/t/how-to-update-workflow-memo-in-typescript/9583/1 "2023-09-23T18:27:57Z")

</div>

Hi!

My understanding of the [memo](https://docs.temporal.io/workflows#memo) is it’s an object that you can update during the workflow that when I do a client.workflow.list() will return the most recent memo data of each workflow it returns.

After looking through the documentation, samples and code in the temporalio/typescript-sdk repo, I can’t figure out how to actually update the memo. I see how you do it in the [Go SDK](https://pkg.go.dev/go.temporal.io/sdk/workflow#UpsertMemo), so I’m pretty sure there’s a way in the Typescript SDK, I just can’t find it.

How do you upsert the memo in the Typescript SDK from the workflow function?

---

<div class="post-metadata">

**Author:** ![bergundy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/bergundy/32/900_2.png) [@bergundy](https://community.temporal.io/u/bergundy)\
**Post date:** [September 24, 2023, 1:54am UTC](https://community.temporal.io/t/how-to-update-workflow-memo-in-typescript/9583/2 "2023-09-24T01:54:22Z")

</div>

This isn’t implemented in TypeScript yet, there’s an open issue for it:

> <https://github.com/temporalio/sdk-typescript/issues/1124>
>
> \### Describe the solution you'd like
> 
> \- Add \`upsertMemo\` command to Workflow A…PI.
> 
> \### Additional context
> 
> \- Underlying support already exists in Core SDK.