Tomorrow marks the 50 thВ anniversary of the decision to move federal support for mass transit out of the Department of Housing and Urban Development, where it began, and into the Department of Transportation, which marked the official switch from thinking of mass transit as primarily an urban affairs program to thinking of it primarily as transportation. The primary purpose, or function, of a government program is used to assign that program its place in the overall budget ( functional classification вЂ“ done in the federal budget at the budget account level) and is often used to determine in what federal department or agency the program should be housed (and which set of Congressional committees have primary oversight of the program). Every federal program has had the following question asked about it at least once: вЂњWhat is the primary purpose of this program?вЂќ It can be compiled but at runtime I get missing method exception for some reason.The question sounds flippant, but from the perspective of the federal role in funding mass transit, the question is crucial. Regarding using UseMessageRetry() and UseInMemoryOutbox(), I'm using message retry in saga definition, but once I've updated to MassTransit 7.2.2 I have a problem with using UseInMemoryOutbox() within saga definition. I'm not sure what 'Used' means and if that could cause this problem. Here is the log when 'authentication service' send request to saga.ДЄnd every time when I get timeout there is a SAGA log within same second with action 'Used' and this action doesn't belong to this request because correlation id is different. I'm not sure is this related to issue but it's happening every time when I get timeout exception. I've checked logs and I've found one pattern whenever I have a timeout. RespondAsync( new ДЄnd here is how caller service call saga: ExecuteAsync( async context =>ДЄwait context. CorrelationIdД®vent(() => GenerateSsoLink, x => x. SetSagaFactory( context => new SsoSessionLinkSagaStateД¬orrelationId = context. Public SsoSessionLinkSaga( ILogger logger = null)Д¬c. Public class SsoSessionLinkSaga : MassTransitStateMachine Sso service saga use Cosmos DB persistence (it was previously used InMemmory and I thoguh this will fix the problem, but it also hapening with Cosmos DB persistence). Here are details about how I setup everything.ДЄll services are hosted in Azure AKS and use RabbitMq as a message broker (also hosted within same AKS cluster in same network). Message has been sent to bus but it doesn't initiate new saga instance. Most of the time everything is working fine, but some of requests from 'authenitcation service' to 'sso service' just timeout without any reason. This 'authentication service' is calling sagas as request/response because process must be done in same request for client. It actually calls 'sso service' saga always and then 'sso service' call 'provisioning service' when needed (provisioning is not always required). There is an 'authentication service', that when complete authentication part, calls these sagas to do provisioning and generate sso link. I'm using publish/subscribe way of communication here.Д«ut the problem is with a caller to these sagas.

And communication between these 2 sagas is OK. One is just 'sso service' to generate URL and the other is 'provisioning service' that orchestrate provisioning activities (I know I could use just one saga but I was playing with it and tried various scenarios). It's specific case since some provisioning is required and a lot of operations must be done in background so I found saga really helpful to orchestrate all operations.

I'm using it in one of my projects and recently I've stuck with one issue. I'm relative new to MassTransit but I really like it more and more.

Masstransit set response address