Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I've got a service endpoint to an Azure Service Bus queue. My compadre wrote an Azure function to forward some SOAP to the accounting system.
I just sent up 20 new productids at once (select 20, publish button.) My plugin handles each one at a time so it becomes 20 messages on the queue. The round-trips back to CE are sequential taking about a minute apiece (first one back in ~2 minutes, last one ~22 minutes.)
However, the Azure function log says none of its round-trips is longer than 10.24 seconds and that the messages are arriving a minute apart.
Where is this process being throttled and why?
I can't imagine CE is putting a minute between each IPluginExecutionContext. So, I'm blaming the Azure Service Bus.
Am I justified and what can be done about it?
Is your plugin step registered as async?
There's no plugin but, yes, the step is async.
My compadre found a setting on the Azure side that controls the frequency of polling the queue. It was set to 1 minute. We tested it at 15 and 3 seconds. Durations diminished to 5 and 2.5 minutes respectively.
Consequence is that Microsoft charges per poll -- 3 seconds is 20 times more expensive than 1 minute.
So, I was right in blaming Azure!
Business Applications communities