# Restarting prodigy on same dataset doesn't skip completed tasks (custom recipe) **URL:** \ **Category:** Uncategorized\ **Created:** [October 4, 2022, 2:51pm UTC](https://support.prodi.gy/t/restarting-prodigy-on-same-dataset-doesnt-skip-completed-tasks-custom-recipe/6005 "2022-10-04T14:51:54Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\ **Post date:** [October 5, 2022, 4:33pm UTC](https://support.prodi.gy/t/restarting-prodigy-on-same-dataset-doesnt-skip-completed-tasks-custom-recipe/6005/4 "2022-10-05T16:33:37Z")
> [@joebuckle](#): > > It seems that we are getting a new session ID every time. Is that the cause of the issue? To set unique session ID's, have you tried to set your [session ID by multi-user sessions](https://prodi.gy/docs/api-web-app#multi-user-sessions) (i.e., add `?session_id=my_session_1` to your URL)? Otherwise, by default Prodigy creates timestamped based session ID's (hence why they're different). However, this shouldn't affect either the input hash (which is created by any values of keys with `"text", "image", "html", "input"`) or the task hash (which concatenates the input hash with a new hash for values from keys named `"spans", "label", "options", "arcs"`) Another possibility, here was an audio user who had issues with their hashing because they accidentally used the keyname `"paths"` (there are several others like this on the default ignore list). Low chance but definitely could be what's explaining this weird behavior. > [@How does "set\_hashes" work ?](https://support.prodi.gy/t/how-does-set-hashes-work/5686/2): > > Hi Jim. You have stumbled apon a keyname that's in the default ignore list and I can totally imagine the confusion. Let's go over it step-by-step. If the key is just text, nothing unexpected is happening. from prodigy import set\_hashes paths = ["a", "b", "c"] [set\_hashes({"text": p}) for p in paths] # [{'text': 'a', '\_input\_hash': -1808989213, '\_task\_hash': -1053809049}, # {'text': 'b', '\_input\_hash': 748838038, '\_task\_hash': -150095526}, # {'text': 'c', '\_input\_hash': -600324218, '\_task\_… --- _[View the full topic](https://support.prodi.gy/t/restarting-prodigy-on-same-dataset-doesnt-skip-completed-tasks-custom-recipe/6005)._