@apeksha-barhanpur

My apologies, I mistakenly believed you had a support plan with FusionAuth (let me know if I am mistaken).

Regarding your question --

Have you had a chance to review the troubleshooting guide that we publish for email?
https://fusionauth.io/docs/v1/tech/admin-guide/troubleshooting#troubleshooting-email

Lastly, a good tip is to remove FusionAuth completely from the email equation by using SWAKS. SWAKS will complete an email exchange with just your email provider credentials (thereby removing FusionAuth from the equation). If SWAKS fails, then would offer good troubleshooting information.
http://www.jetmore.org/john/code/swaks/

Thanks,
Josh

I tried with all HTTP methods enabled for /api/user only, and it update user successfully.
But if I tried only with GET and PATCH methods enabled for /api/user , I get 'statusCode=401'.
Here is code

import { FusionAuthClient, UserRequest } from '@fusionauth/typescript-client' ... export class FusionAuthService { private fusionAuthClient: FusionAuthClient; constructor(private context: Context) { this.fusionAuthClient = new FusionAuthClient(context.config.fusionAuth.apiKey, context.config.fusionAuth.apiUrl); } ... public async updateUser(userId: string, userRequest: UserRequest ) { return this.fusionAuthClient.updateUser(userId, userRequest) .then(clientResponse => { logger.info("User:", JSON.stringify(clientResponse.response.user, null, 2)); }).catch(logger.error); }

here is invocation of updateUser method that happens on 'user.registration.create' event

if (user) { const patchBody = { user: { email: event.user.email, data: { userId: user.id } }, } await this.fusionAuthService.updateUser(event.user.id, patchBody); }

Now I understand that I use updateUser method and I don't know what kind of HTTP request it used.
I have found patchUser and with it get success.

Thanks for your help.

You can use the database.maximum-pool-size value in the fusionauth.properties file prior to 1.19.x ( it was just not documented) , but if you want to use the environment variable version is not available until 1.19.x.

You could look at kickstart: https://fusionauth.io/docs/v1/tech/installation-guide/kickstart

This would be a good fit if the other devs fusionauth instances are going to be starting from scratch.

Otherwise you might want to vote for https://github.com/FusionAuth/fusionauth-issues/issues/560 which talks about a different path forward (which is as of now unimplemented).