About Request Types and Statuses

When you perform different data configuration tasks, you can review the different types of requests involved with those tasks in the Request History area.

One Time Request Types

Request Type	Description
Custom Attribute Mapper	A Netsuite-specific request run. See Map Custom Attributes.
Data Source Reset	A request to reload complete data for a data source. See Reset and Reload the Data Source.
Delete Custom Data Configuration	A request to delete a custom data configuration. See Extend Data with Custom Data Configurations.
Delete Connection	A request to delete a connection to a data source. See Manage Data Connections.
Deploy Custom Data Configuration	A request to deploy a custom data configuration in the data warehouse. See Extend Data with Custom Data Configurations.
Frequent Data Refresh Publish	A request to publish the frequent data refresh configuration. To view the status of frequent data refreshes, go to the Recurring tab. See Configure Frequent Data Refresh V2 (Preview) and View Request History.
Full Load (Adhoc)	A full load run that happens on activation of modules such as functional areas. See Activate a Data Pipeline for a Functional Area.
Full Load (Scheduled)	A request to schedule a full load run on activation of modules such as functional areas. See Activate a Data Pipeline for a Functional Area.
Generate Custom Data Configuration	A request to generate a custom data configuration. See Extend Data with Custom Data Configurations.
Module Reset	A request to refresh the data in the data warehouse for the functional area. See Reload Data for a Data Pipeline.
Publish Custom Data Configuration	A request to generate and deploy a custom data configuration in the data warehouse. See Extend Data with Custom Data Configurations.
Refresh Data	The system ran a request to refresh data. See Schedule Incremental Data Refreshes.
Reload Data (Next Data Maintenance)	A request to reload data in the next scheduled data maintenance. See Schedule Data Maintenance.
Reload Data (Next Refresh)	A request to reload warehouse data in the next scheduled data refresh. See Reload Data for a Data Pipeline.
Reset & Reload	A request to reload warehouse data for a data source. See Reset and Reload the Data Source.
Reset Data Warehouse	A request to reset the warehouse. This reset deletes all the customer-added warehouse data. See Reset the Data Warehouse.
Test Connection	A request to initiate test connection for a data source. See Manage Data Connections.
Undeploy Custom Data Configuration	A request to remove data from the warehouse while retaining the custom data configuration. See Extend Data with Custom Data Configurations.

Recurring Request Types

Request Type	Description
Scheduled Data Refresh	Incremental data refresh that is performed according to the Data Refresh schedule in Pipeline Settings. See Schedule Incremental Data Refreshes.
Frequent Data Refresh	Intra-day refreshes performed according to the Frequent Data Refresh schedule using the original refresh mechanism. See Schedule Frequent Data Refreshes.
Frequent Data Refresh V2	Intra-day refreshes performed according to the Frequent Data Refresh schedule using the revised refresh mechanism. See Schedule Frequent Data Refreshes.
Data Maintenance	Data refresh that is performed as part of data maintenance for full data reloads with incremental refresh. See Schedule Data Maintenance.

One Time and Recurring Request Statuses

Request Status	Description
Completed	The request ran successfully and is now complete.
Failed	The request has failed. Typical reasons are if you've selected unsupported columns in data augmentation or there are failures related to bundles.
In Progress	The request is running. The request is resolving.
Not Required	The request isn't required.
Queued	The request is queued. Most common reasons are: Another request is in progress for the same source. The warehouse reset request may be in progress. The data source health may be bad. The required dependent functional area or custom data configurations aren't activated
Received	The request is submitted.
Rejected	The request is rejected. Typically this status is sent if you need to make changes and the request can't be completed. The system displays the applicable reason for rejection on the user interface.
Scheduled	The request is scheduled to run.
Skipped	The request has been skipped. Potential reasons are: The previous request overran the next scheduled run of the repeating request. There is nothing to execute because no functional areas are activated.
Troubleshooting	The request is taking a long time and Oracle is investigating it.
Unscheduled	The request has been unscheduled because you changed the schedule.