Ocelot API Gateway: Intermittent 'Failed to Load API Definition' When Idle

[robbypranata010118]

I am developing an application using

• Ocelot as an API gateway,
• Consul as the service discovery,
• and .NET 7 for the web API.

I’m actually not sure where this issue originates – whether it’s from Ocelot, Consul, or the web API that I created. The issue I’m facing is that sometimes Ocelot's Swagger responds with "failed to load API definition,"
even though when I check in Consul, the web API service is still registered and in a healthy status.
I’ve also checked, and the web API can be accessed directly if I go to the downstream address.
I suspect this issue happens when the application is idle for a certain period without any access. So far, my workaround has been to restart the web API service to get it working again.

(FYI, my web API is deployed on IIS, and I’ve set the idle timeout to 0.)

Has anyone else experienced this, and how did you handle this issue?

[raman-m]

Robby, officially Ocelot team doesn't support any Swagger features.
As a workaround, you can ask your questions in the MMLib.SwaggerForOcelot project repository.

[raman-m]

@Burgyn, could you help Robby, please?