Jathan McCollum

> Update: > > I am still running version 1.4.2. Is the fix available in a later version already? I just had this happen on a scheduled job. As soon...

> @bryanculver I did restart all workers + scheduler after upgrading to 1.4.5, so I hope that did the trick. > > If I remove `CONN_MAX_AGE` entirely, won't it behave...

Alright @joaopsys thanks for the update. Will definitely have to try to reproduce this. As for the issue with the scheduled jobs. If they weren't running before and were "due"...

> * METRICS_ENABLED / NAUTOBOT_METRICS_ENABLED This one can't easily be set as an environment variable because it's a "magic" setting that is interpreted. The magic variable is processed inside of...

We won't be able to get to this immediately, but it's worth noting that a [similar change was made in NetBox 2.11](https://github.com/netbox-community/netbox/issues/4999). We would happily welcome contributions from anyone willing...

I am of the mind that we fix this in finality in v2.x using [`django-import-export`](https://django-import-export.readthedocs.io/en/latest/) and put this issue to rest without having to maintain the problem ourselves.

In debugging a little with @gneville-ot on Slack, I have a root cause at least for the issue with static files when `NAUTOBOT_DOCKER_SKIP_INIT=True` is set. This results in `nautobot-server post_upgrade`...

Thanks @joaopsys for the in-depth debugging. Seems like this can result in some extra documentation and a small fix here.

Inventory of changes needing to be made to satisfy this based on `2.0 TODO` comments in the code base, broken down by filename: ``` nautobot/core/graphql/generators.py - # 2.0 TODO: #824...

> Is there something like [Issue #2171](https://github.com/nautobot/nautobot/issues/2171) planned as an enhancement too? That flew under my radar, and I don't think it's out of the realm of possibility for 2.x,...