We’re trying to implement alerting around the service that loads work into PSO daily. To do this, we’d like to better understand what an internal ID of 0 represents. In some cases, it seems to indicate success (e.g., when creating unavailabilities), while in others, it suggests a failure (e.g., when bad data is loaded into PSO).
We've noticed that PSO returns a 0 after our daily loads when a record results in a duplicated key (bad data). Are there any other reasons why a LOAD to PSO might return a 0 besides this scenario?