We noticed that the updatedAt in the forecasts endpoint can be months older than the updatedAt in the outputs endpoint. For instance, I’m looking at a forecast with an updatedAt of 1/31/25 in forecasts, but most of the wells have an updatedAt of around 3/5/25 in the outputs endpoint.
I was expecting the updatedAt in the forecasts endpoint to be the latest updatedAt from outputs, but that doesn’t appear to be the case.
I’m curious if this is intended, and if so - what is the updatedAt in forecasts referring to?
Hey Kyle,
There is a similar question asked in the past on here if you want to check it out in regards to projects endpoint.
The short answer is that updatedAt in the forecasts endpoint would only be changed if you changed the name of the forecast or added/removed tags.
We don’t update the updatedAt date-time if the forecast runs or if you modify the parameters, etc. We also don’t modify updatedAt if you convert the forecast.
The best way for you to ensure that the forecast has been modified from the forecasts endpoint would be to check the rundate, which is updated when the forecast is run.