Copying to Azure Blob fails intermittently with error Bad request

[sheikhsharoon]

Service : Azure Blob, ,Kurbernetes
SDK: 3.1.401
Platform : .Net Core 3.1
Error encountered :
Copying to azure blob fails with the error . Bad request

Microsoft.Azure.Storage.StorageException: Bad Request
at Microsoft.Azure.Storage.Core.Executor.Executor.ExecuteAsync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext, CancellationToken token) at Microsoft.Azure.Storage.Core.Executor.Executor.<>c__DisplayClass0_01.b__0()
at Microsoft.Azure.Storage.Core.Util.CommonUtility.RunWithoutSynchronizationContext[T](Func1 actionToRun) at Microsoft.Azure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext)
at Microsoft.Azure.Storage.Blob.CloudBlockBlob.UploadFromStreamHelper(Stream source, Nullable`1 length, AccessCondition accessCondition, BlobRequestOptions options, OperationContext operationContext)
at Microsoft.Azure.Storage.Blob.CloudBlockBlob.UploadFromStream(Stream source, AccessCondition accessCondition, BlobRequestOptions options, OperationContext operationContext)
at Microsoft.Azure.Storage.Blob.CloudBlockBlob.UploadFromFile(String path, AccessCondition accessCondition, BlobRequestOptions options, OperationContext operationContext)
at syngo.Cloud.PM.TenantSpecificDataExtractor.CloudAccess.CloudAccessor.CopyAllFilesToAzureContainer(String sourceDirectoryPath, String privateStoreConnectionString, String destinationContainerName, String destinationDirectoryName) in /home/vsts/work/1/s/Source/PM.TenantSpecificDataExtractor/CloudAccess/CloudAccessor.cs:line 157
Request Information
RequestID:
RequestDate:Wed, 23 Sep 2020 07:05:43 GMT
StatusMessage:Bad Request
ErrorCode:

This exception occurs when copying to azure blob storage from a web job hosted in kubernetes
In order to investigate this issue , we have tried the same logic from a console application and from a locally hosted web job . We could not reproduce the error.
Can you help us investigate this further?