Hello. We are hosting our python backend SDK in a Lambda connected to API Gateway. This Lambda behaves correctly for the signup/signin flow. We are trying to spin up another Lambda API Gateway service in a different repository and use supertokens to authenticate these endpoints. To use the supertokens verify_session function in this new repository, we need to call

init

. Doing so in this new Lambda, the call to

init

is timing out. My thought is that since the

InputAppInfo

object has the same api_base_path, and api_domain as the first Lambda,

init

might be timing out because a backend SDK with those values already exists. Would this be a reason for

init

timing out? If that is the case it seems like we would have to include all of our API endpoints across the organization in a single Lambda in order to have session authentication on those endpoints.