You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have been trying out the AGgregateContextByTenantId strategy as highlighted in the official nestjs doc and i am facing a strange behavior, whereby the contextId / tenantId is correctly persisted, the provider object is not reconstructed at any time (i.e. it is indeed "durable") but somehow the sequelize configs do not get changed when previously used tenantIds make their second requests ...
very strange ... is it something you have also experienced perhaps ?
The text was updated successfully, but these errors were encountered:
thanks a lot for providing this example repo.
i have been trying out the AGgregateContextByTenantId strategy as highlighted in the official nestjs doc and i am facing a strange behavior, whereby the contextId / tenantId is correctly persisted, the provider object is not reconstructed at any time (i.e. it is indeed "durable") but somehow the sequelize configs do not get changed when previously used tenantIds make their second requests ...
very strange ... is it something you have also experienced perhaps ?
The text was updated successfully, but these errors were encountered: