# Persistent error with make.com 'search for record' noloco timing out \[500\]

**URL:** <https://community.noloco.io/t/persistent-error-with-make-com-search-for-record-noloco-timing-out-500/1878>\
**Category:** Bugs\
**Created:** [April 17, 2025, 5:00pm UTC](https://community.noloco.io/t/persistent-error-with-make-com-search-for-record-noloco-timing-out-500/1878 "2025-04-17T17:00:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![seanvosler](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/seanvosler/32/698_2.png) [@seanvosler](https://community.noloco.io/u/seanvosler)\
**Post date:** [April 17, 2025, 5:00pm UTC](https://community.noloco.io/t/persistent-error-with-make-com-search-for-record-noloco-timing-out-500/1878/1 "2025-04-17T17:00:29Z")

</div>

![Screenshot 2025-04-17 at 9.56.27 AM](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/b/b2ee248d1a40015d7240c51832ceb3b0d00caa6d.png)

I’ve tested different other unique identifiers outside of email with no luck. Seems to be a recent issue (within 48 hours) related to the ‘search’ module in make specifically.

Will keep an eye out for it it resolves itself, could be a [make.com](http://make.com) issue and not a noloco issue, but quite a common used module, worth looking into!