@fordN and I had done some work over in the agent on this but found the root issue to be this field. Here is the indexer-agent PR graphprotocol/indexer#958

@dwerner we'd need to address the root cause here, the paused field should never be null, it should either be true or false, The only reason i can see that a null field is possible there is when the deployment_schemas table doesn’t have the subgraph_hash we are looking for, im not sure if thats even possible.
If that is the case then the paused field gets populated with a None.

This is the part of the code where paused gets populated

To address the root cause we'll need to inspect the database if this is reproduced somewhere

Closing this as a root cause fix is preferred

In a conversation with @lutter and @fordN, deployments can exist where assignments do not. Then this being bool! fails where an assignment does not exist. So this is the correct way to express this. Just like the node field above it.

@lutter's pretty diagram. Thanks for helping me understand what's going on here.