# API Gateway internal server error

**URL:** <https://forum.datomic.com/t/api-gateway-internal-server-error/678>\
**Category:** Datomic Cloud\
**Created:** [October 24, 2018, 9:49pm UTC](https://forum.datomic.com/t/api-gateway-internal-server-error/678 "2018-10-24T21:49:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![marshall](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/marshall/32/48_2.png) [@marshall](https://forum.datomic.com/u/marshall)\
**Post date:** [January 14, 2019, 8:02pm UTC](https://forum.datomic.com/t/api-gateway-internal-server-error/678/8 "2019-01-14T20:02:11Z")

</div>

I should be more clear - cycling the Datomic process is _one_ thing that can cause this issue. Anything that disrupts the Lambda-Datomic Node connection will likely do so. I suspect there are a number of Lambda timeout-related issues that can cause a similar issue.

If you’re unable to implement a retry strategy at the client-side of this interaction, I’d suggest either doing what you did (move to an instance that runs your client) or use the (upcoming) non-lambda connection that will allow API gateway to call directly to the Datomic Node.

---

_[View the full topic](https://forum.datomic.com/t/api-gateway-internal-server-error/678)._
