I think this issue is only because of MongoDB, we are suing Azure CosmosDB with Mongo API Version 3.6 also. It has already issue present from last 2 months https://support.abp.io/QA/Questions/473/MongoDBDriverMongoCommandException-Command-aggregate-failed-Error2-After-deployment-on-Azure-using-CosmosDB.
Due to above issue we have choose to use 3.2 version for mongo in Cosmos and we started working. But when we want to implement Backgroung job its not working.
We have to use MongoDb only. Please suggest a workaround above issues. It has performance issue, Aggregation Issues, Background job is not getting triggered.
@Alper Above issue remains same after migrating app to 3.2.1 with MonogDb
I know i checked, nothing gets logged and brekpoint also gets move to step after EnqueAsync();
Hi @maliming, Nothing gets logged, dont know why, The job that was working multiple times and suddenly it stopped without making any changes in code. Is job getting triggered at your end? if yes please provide us that working sample.
@maliming Could you please revert urgently on above ? We are pressed for time for importing client data and this Background job working is very crucial .
Sample code Added.
I have shared a project with you on git. Please let me know! Thanks
@Alper Could you please provide the necessary steps like should i download latest commecial project or As i am using ABP Commecrial Version v3.1.2 in that where i need to make changes. Please provide the link that will guide us.
Hello, We cannot use EF CORE as we are strictly developing the app using MongoDB.
Hello, Please send me the link how we can extend it without adding. Actually its a other part. My main issue is why its not redirecting to Dashboard page after login?
