Backstage Entity Registration takes too long | Backstage | Page 1

sleek steeple Nov 28, 2025, 10:07 AM

#

Hello everyone.

I'm experiencing a weird behavior with Backstage in prod, hosted in an AKS cluster. When testing locally, I can create entities and their catalog-info.yaml files in GitHub and they immediately appear in the catalog, but in prod, they get added to the locations but are not immediately visible in the catalog. It takes about 10-15 minutes for them to appear, which does not provide great UX. I increased resources in the cluster but that didn't help. Added GitHub webhook integration to listen to repo pushes, I do see the event logs but the entities are still not visible in the catalog API.

I don't know if there's anything I missed or if anyone's experienced this before. Any help will be greatly appreciated.

Thanks

elder jackal Nov 28, 2025, 12:29 PM

#

This is likely because your catalog.refreshInterval is set too low for the number of entities you have - such that it is perpetually behind on processing, because it piles up faster than it can work it down.

#

There's an otel metric for that to track it

#

We generally have a delay of a few hundred milliseconds.

sleek steeple Nov 28, 2025, 1:23 PM

#

Thanks for your response @elder jackal

We have very few entities in GitHub

I suspect the issue might be the # of the imported Azure AD users. We set this schedule for user refresh to be a bit longer though

is there a way to sync/stitch a catalog-info.yaml file based on github pushes?

Thanks again

elder jackal Nov 28, 2025, 1:41 PM

#

Note that I was referring to the processing interval - not the schedule that you have set for user ingestion.

#Backstage Entity Registration takes too long