Error Messages

403

I

Tenant does not have any valid license

Users do not have a valid license to use AFA

Log the issue on the support portal.

409

I

There is a current job in progress

A job is currently in the queue, so AFA prevents you from starting another forecast or analysis to avoid potential calculation errors caused by value changes.

View the Job Queue.

500

E

Internal Server Error

This error indicates that AFA does not know how to handle that last request. Try refreshing the browser.

There can be many reasons why this occurs, so to help us track it down, provide us with more details and log the issue on the support portal.

502

E

Bad Gateway

This would indicate that the server is not ready and receives an invalid response. Try refreshing your browser, this will solves 90% of the issues.

If the problem persists, provide us with more details and log the issue on the support portal.

503

E

Service Unavailable

The service is unavailable to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

If the problem persists, provide us with more details and log the issue on the support portal.

600

W

Analytics Failure : No data to evaluate slope

There is not enough data. Analytics will not work on this dataset.

601

W

Decline Analytics Failure : not enough positive rate data for smart fit. Decline parameter values should be entered manually for both operational and profile forecast.

There is not enough data. decline analytics will not work on this dataset. Possible causes:

• dataset does not have enough data

• project settings filter out too much data

• selected cluster start day filters out too much data

• decline curve cannot be interpreted from data

If the project setting and cluster start day are correct, the user should disable smart fit and auto update cluster start day. They should then manually enter the desired decline parameters into the operational and profile forecast.

602

W

Decline Analytics Failure : No clear negative trend

Selected data does not have a clear declining trend. Decline analytics will not work on this dataset. Possible causes:

• dataset does not include a decline

• project settings filter out declining trends

• selected cluster start day filters out declining trends

If the project setting and cluster start day are correct, the user should disable smart fit and auto update cluster start day.

603

W

Decline Analytics Failure : not enough positive rate data. Start day requires manual input.

The user should disable cluster analysis in this scenario and manually enter an appropriate value. If there is no reason to exclude early time data, the value 0 is appropriate.

604

W

FMB Analytics Failure : No clear negative trend

Selected data does not have a clear declining trend. FMB analytics will not work on this dataset. Possible causes:

• dataset does not represent a depleting reservoir

• project settings filter out section of data where reservoir is depleting

605

W

Decline Analytics Failure : Smart Fit cannot find appropriate initial rate

Decline smart fit cannot find initial rate higher than the economic cutoff

• economic cutoff too high

The user should reduce economic cutoff or turn off smart fit and manually input decline parameters

606

W

KOLDUN Inputs Failure: Forecast End Date needs to be provided

KOLDUN forecast cannot run without Forecast End Date

• Forecast End Date under Project settings needs to be provided by the user

607

W

RULON: Cannot Calculate

There are no saved analyses selected to calculate rollup forecast

use RULON: Group Runs perform analyses on multiple wells

608

W

RULON: Cannot Export

There are no saved analyses selected to export rollup forecast

use RULON: Group Runs perform analyses on multiple wells

609

W

KOLDUN: dependency matrix failure

There are too many variables correlated to each other.

The user needs to decrease the number of variables correlated to each other at dependency matrix based on Cholesky decomposition analysis.

610

W

Analytics Failure : No positive slope found

Attempted algorithm cannot find a positive slope

Currently automated algorithms which cause 610 & 611 cannot be recovered from. This is a known issue and will be addressed in future releases.

611

W

Analytics Failure : No Negative slope found

Attempted algorithm cannot find a negative slope

Currently automated algorithms which cause 610 & 611 cannot be recovered from. This is a known issue and will be addressed in future releases.

612

W

Project Setting start date remove all data

There is no data before project setting start date

613

W

Project Setting end date is before data start date

Forecast cannot be performed, project setting end date is before data start date.

614

W

Analytics Failure : No oil rate greater than zero to evaluate WOR

There is not oil rates or oil rates are zero. Analytics will not work on this dataset.

The dataset needs to have enough oil rates greater than zero to be performed.

615

W

RTA / FMB Analysis Impossible : No positive rate values in dataset to perform analysis on

Possible causes:

• dataset does not have enough positive rate data

• project settings filter out too much data

616

W

WOR Analysis Impossible: Water Cutoff is too low.

Water Cutoff input is too low. Analysis cannot be completed.

The water cutoff is much lower than available water rates. This cause inconsistency in the analysis.

617

W

WOR Export Impossible: There is no forecast end date specified.

There is no forecast end date specified in project setting. No forecast results can be exported to csv.

WOR forecast method involved forecasting with a constant liquid rate. If a project end date is not specified forecast may not complete

618

W

Not enough unique x data to calculate gradient on

619

W

Cannot calculate wellhead IPR with no layers

No reservoir layers have inflow performance

700

E

Dataset Validation Error

The uploaded dataset did not pass validation checks.

It can be:

• The uploaded dataset did not pass validation checks.

• The dataset content is invalid (no dataframe was generated).

• The dataset is missing required Well Name information.

701

E

File Upload Failed

An error occurred while uploading the file to storage

702

E

Save Dataset Tags Failed

Failed to save dataset tags to the database.

703

W

Well already exists

A well with the same name or identifier already exists in the system.

Uploading this file will override the existing data for the well