I am able to pull forecast parameters through the ‘get-forecast-outputs’ endpoint but encountered an error with a newly created forecast.
I can pull parameters for any other forecast in any other project without issue. However, I created a new forecast where I replaced all my parameters with various other forecasts and the api output is displaying that there are no forecasted parameters tied to any of the wells.
When reviewing the API documentation, I noticed the structure is dependent on the [forecasted] column value being equal to ‘true’. All my wells are returning ‘false’ and only a small subset of the wells seems to be getting returned.
Making a copy of the forecast gives the same error and I don’t believe there is anything wrong with my endpoint call (pagination not working, incorrect syntax, etc). Has anyone else encountered this error or has found a remedy to this?
Update
I got a new forecast to work through a workaround but I believe something is messed up on the backend of the non-working forecast. Some of my QAQC is below.
Initial Test: Created new forecast and replaced parameters using existing prior forecasts = api does not register forecasts
- QAQC Step 1: Proceed to clear forecast parameters and then auto forecast all wells = api registers forecasts
- QAQC Step 2: Proceed to replace parameters using existing prior forecasts = api does not register forecasts
New Test: Create entirely new forecast and import the forecast parameters via csv import from the same non-working forecast = api registers forecasts
Are you using the Replace Forecast Parameters functionality for this test?
An issue has been identified with the Replace Forecast Parameters functionality in the UI. This is currently being prioritized
1 Like
When you get a moment, could you retry your process? I just pushed a change that I believe should fix your issue
1 Like
@Jeff_Hopkins Confirmed that the issue has been fixed! I ran through the entire process, and everything is populating correctly now. I appreciate your help with this.
A tad late but confirming I used the ‘Replace Forecast Parameters’ when initially populating forecasts.