Extraction Logs
A guide to extraction logs in Fynapse.
Overview
This article provides information about extraction logs, which comprise data extracted using defined extract configurations.
The Extraction Logs screen allows you to view details of data extracts run in Fynapse (also using Fynapse REST API) to verify, for example, which data was extracted, what is the progress status and who triggered it.
Extraction Logs Screen
The Extraction Logs screen comprises the following elements:
- The Refresh button - click it to see if any new extractions were triggered or if the statuses of already triggered ones have changed
- The grid - use it to see information about finished and still running data extractions. The grid has the following columns:
- Extract name - an automatically created name of a particular extract file. The name has the following syntax: a configuration name and a start date and time (UTC). For example, daily_extract_2022-08-05_12-00-00. When the Target status is Sent, you can click the extract name to download it. Note that you will not be able to download data from the extract file triggered via REST API and its name will not contain a start date and time.
If you selected the Split per Posting Date checkbox, then the extract file name includes also the Posting Date after the configuration name. For example, daily_extract_2023-06-12_2023-06-13_12-00-00.
- Started on - a date and time of the extraction process start (in a local time zone)
- Uploaded on - a date and time (in a local time zone) when the extract file was placed on the cloud storage. If the extraction or upload process failed, then there is no information about the date and time.
- Extraction status:
- Pending - when Fynapse collects data that will be extracted, but the extraction process itself has not started yet. At this point, we recommend running the same extract configuration again, especially for the incremental extraction.
- Duplicated - when a user triggered the extraction process again for an incremental extract already in the Pending status. Such extraction will not be performed at this point, and it will not be possible to run it automatically or manually until it reaches at least the In progress status.
- In progress - when the extraction process is happening
- Completed - when the extraction process ended successfully
- Failed - when the extraction process did not succeed
Note that for the following situations:
- Extraction status is Failed or Extraction status is Completed, but Target status is Not sent - the extraction process will be automatically rerun until it ends successfully, or reaches an end date set for the extract configuration this process uses.
- Extraction status is Completed, but Target status is Missing manifest - the system will retry to generate the manifest file several times, but the extraction process itself will not be rerun automatically. If you need to rerun the extraction, please do it manually.
- Completed (no data) - when the extraction process has ended successfully but an extract file does not contain any data
- On hold - this extraction status can be displayed when the Split per Posting Date option is selected. It appears when the extraction process was canceled because Fynapse detected only data for the Posting Date that was extracted before (some of the records were not included in this extraction because they appeared after the extraction took place). In such a situation, data will be extracted when the next extraction is triggered.
- Target status:
- Pending - the extraction process is in progress or has already finished, but the extract file has not been uploaded yet
- Sent - upload completed successfully
- Not sent - upload did not succeed
- Pending manifest - generation of a manifest receipt file is in progress
- Missing manifest - generation of the manifest receipt file did not succeed. The system will retry to generate the manifest file again.
The Pending manifest and Missing manifest statuses are available only if the generation of the manifest receipt file is required. To learn when the manifest receipt file is generated, refer to the Manifest Receipt File section in the Data Extraction chapter.
- No information about the status in this column means that the uploading process was not started because the extract file is empty, and empty files are not sent to the cloud storage
- Target space - information about the upload space to which the extract file will be uploaded. If the extract file is triggered via REST API, its data is presented in your API tool. All extracted files are placed on a cloud storage and can be found in dedicated paths. The general path structure is:
<namespace>/<entity>/extracted/<FILE_NAME>for example: fynapse/Journal/extracted/Journal Increment_2025-12-15_15-04-23.csv. - Executed - the way in which the extraction process was started. It can be done manually (triggered by a user by clicking the Run now button) or automatically (initiated by a system according to a particular schedule).
- Generated by - displays who triggered the extraction process. If the extraction was started by:
- The system, then a column cell is empty
- The user, then the username is displayed
- Configuration name - the name of the configuration on which basis the extract file was created. You can click the configuration name to be redirected to the configuration details.
- Error message - the column contains errors thrown during the extraction process, for example, errors connected with using invalid Fiscal Calendars while configuring dynamic date attributes filtering. To learn more about this configuration, refer to the Dynamic Date Attributes Filtering section.
- Journals - the column contains the Open journals link that will redirect you to the Journals screen in Subledger with the Journal Summary Id set as the search criterion. The screen will display all Journals that were included in the aggregation in the selected extract file. This option is available only when Journal was selected as a data source and the Aggregate Journal data checkbox was selected while configuring the extract. To learn more, refer to the Extract Configuration chapter.
- Actions - click the More button to see all actions that you can perform for the particular extract:
- Rerun - an action available for extracts that have the Completed or Failed status for the Extraction status. However, the rerun action might not be available for some extracts that have the Failed status due to configuration errors or the fact that the Entity for which the extract was run does not exist anymore. After clicking the Rerun option, a selected extract is run again. The Rerun option is unavailable for extract files triggered via REST API.
- Extract name - an automatically created name of a particular extract file. The name has the following syntax: a configuration name and a start date and time (UTC). For example, daily_extract_2022-08-05_12-00-00. When the Target status is Sent, you can click the extract name to download it. Note that you will not be able to download data from the extract file triggered via REST API and its name will not contain a start date and time.
Additionally, you can:
- Sort columns ascending or descending and set their visibility by clicking the three dot icon next to the names of columns
- Filter content within each column to find particular information
In addition, at the bottom of the screen, you can:
- See the number of pages that display extraction logs and buttons to navigate between pages
- See the information which page you are currently viewing and how many pages are available in total
- Decide how many extraction logs you want to display on one page
- See how many extraction logs are presented on the page
Turorials
How to Rerun an Extract?
Only extracts that have the Completed or Failed status for the Extraction status can be rerun. However, some extracts cannot be rerun due to configuration errors or the fact that the Entity for which the extract was run does not exist anymore. In such a case, the rerun action will not be available even if the extract has the Failed status.
- Go to Integration > Extraction Logs.
- In the grid, find an extract file that you want to rerun.
- In the Actions column, click the More button.
- Click Rerun. The extraction process will start and once it is finished, you will see a proper extraction log in a new row with a re-run suffix and the extract file will be placed on the defined cloud storage. To see the extraction log in the grid, click the Refresh button.
How to Download an Extract File?
Operating under Feature Flag If you want to use this feature, contact your System Administrator.
To download an extract file, its Target status must be Sent.
- Go to Integration > Extraction Logs.
- In the grid, find an extract file that you want to download.
- Click the extract file name.
- You may be prompted to provide a location where the extract file will be saved or the location will be automatically selected (it depends on your web browser configuration). The extract file will be downloaded.
How to View Journals Used in Aggregation in a Particular Extract File?
- Go to Integration > Extraction Logs.
- In the grid, find an extract file that contains the aggregation that details you want to view.
- In the Journals column, click the Open journals link. You will be redirected to the Subledger > Journals with Journal Summary Id set as the search criterion, where you can view all Journals included in the aggregation.
