# Replay for non-deterministic change

**URL:** https://community.temporal.io/t/replay-for-non-deterministic-change/8572
**Category:** Community Support
**Tags:** go-sdk
**Created:** [June 20, 2023, 7:44am UTC](https://community.temporal.io/t/replay-for-non-deterministic-change/8572 "2023-06-20T07:44:22Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [June 21, 2023, 3:34pm UTC](https://community.temporal.io/t/replay-for-non-deterministic-change/8572/3 "2023-06-21T15:34:56Z")

</div>

Hello @Kevin_Meng

I guess there are some edge cases in which the SDK does not compare the activity name on replay.

Can you try the following?

```auto
- activityA
- sleep
- activityB

```

when the workflow reaches sleep, stop the worker and swap activityA and activityB, and start the worker again

```auto
- activityB
- sleep
- activityA

```

When the timer fires you should get a non-deterministic error.

Let me know how it goes.  
Antonio

---

_[View the full topic](https://community.temporal.io/t/replay-for-non-deterministic-change/8572)._