loadbuilder | Node package for building combine | Runtime Evironment library

You can't use InstancePerRequest unless the object being resolved is part of a web request (as noted by the comments on the question). More specifically:

• The executing application must be a web application.
• The executing application needs to have the Autofac web integration in place.
• The resolution must be happening in that web application as part of a response to an inbound web request - for example, as part of an MVC controller or ASP.NET Core middleware.

The "per request" semantics have nothing to do with the client making the request - it's about the server handling the request.

You might want to spend some time with the documentation on the topic. There is a section in there about how to implement custom per-request semantics for your app.

If what you are creating is a console app that takes in requests from clients (e.g., a self-hosted web application) then you need to:

• Add the existing Autofac web integration for your app type (we do support ASP.NET Web API and ASP.NET Core self hosted scenarios); OR
• Implement something custom if you're not using ASP.NET (see that doc I linked).

If what you are creating is a console app that issues requests as a client then you should ignore InstancePerRequest. Instead:

• Create a new lifetime scope around each request (like you're doing) and treat that as a unit of work.
• Register components as InstancePerLifetimeScope so there will be just one for the duration of that lifetime scope.

That said, without a minimal repro it's hard to see what you're doing beyond that to provide any sort of guidance.

Since you mentioned you're pretty new to all this, it would be very worth your time checking out the Autofac documentation to start understanding concepts like this as well as looking in the Examples repo where there are working examples of many different application types to show you how things work.