# Migrate-wizard gets to 72% and then returns error

**URL:** <https://org-roam.discourse.group/t/migrate-wizard-gets-to-72-and-then-returns-error/2026>\
**Category:** Troubleshooting\
**Created:** [September 9, 2021, 9:55pm UTC](https://org-roam.discourse.group/t/migrate-wizard-gets-to-72-and-then-returns-error/2026 "2021-09-09T21:55:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![northjayd](https://avatars.discourse-cdn.com/v4/letter/n/f17d59/32.png) [@northjayd](https://org-roam.discourse.group/u/northjayd)\
**Post date:** [September 9, 2021, 9:55pm UTC](https://org-roam.discourse.group/t/migrate-wizard-gets-to-72-and-then-returns-error/2026/1 "2021-09-09T21:55:06Z")

</div>

It returns

`Wrong type argument: arrayp, nil`

and then none of my files show up when I do org-roam-node-find

I also tried org-roam-setup and that also gets to 72% before returning the same error.

I commented out everything regarding roam from my config. And I’m on doom emacs latest version.

Any help would be huge because otherwise I have no idea what I would do

---

<div class="post-metadata">

**Author:** ![nobiot](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/nobiot/32/159_2.png) [@nobiot](https://org-roam.discourse.group/u/nobiot)\
**Post date:** [September 10, 2021, 7:06am UTC](https://org-roam.discourse.group/t/migrate-wizard-gets-to-72-and-then-returns-error/2026/2 "2021-09-10T07:06:19Z")

</div>

It’s probably caused by data in one or some of your notes – e.g. you specified `#+ROAM_ALIASES` or `#+ROAM_REFS` with no value.

If I were you, I would try 3 things, probably in this order (because it’s easier to try 1 than 3).  
The objective is to find an/some offending note(s).

1. Turn on `toggle-debug-on-error` and run the same thing. It might give you the file name that causes this issue
2. Use grep or ripgrep (or whatever file search program you can use) to look for ROAM\_ALIASES, ROAM\_REFS, etc. to see if there is any one that has no value
3. Move half of the notes somewhere else, and run the same thing. Repeat this to narrow down the number of notes, and try to find which file(s) cause the error

If you have headings with IDs, you might need to do this per node, rather than the file.
