# Jobs History ## Jobs History The **Jobs History** page is your central logbook for all automated file transfer activities executed by your devices. Every time a job runs - whether it’s moving files locally, retrieving them from an FTP server, or importing from a file share - it leaves a detailed record here. This history is essential for monitoring operational health, verifying that data pipelines are functioning as intended, and diagnosing issues when they occur. By combining a high-level job overview with in-depth execution logs, the **Jobs History** page allows you to quickly spot trends, confirm successful transfers, and troubleshoot failed runs - all in one place. Whether you’re ensuring that scheduled jobs keep your data flowing or investigating why a particular file didn’t arrive, this is the go-to location for understanding what happened, when it happened, and why. *** ### Jobs History The **Jobs History** page provides a complete overview of file transfer jobs that have been executed on a device. These jobs can include: * [**File Jobs**](/management-portal/designer/assets/jobs/file-job.md) * [**FTP Jobs**](/management-portal/designer/assets/jobs/ftp-job.md) * [**File Share Jobs**](/management-portal/designer/assets/jobs/file-share-job.md) Jobs will appear on this page if they have been configured from an **Asset Hierarchy** and that hierarchy has been deployed to a device. *** ### Acessing Jobs History If an **FTP Job, File Share Job** **or File Job** is configured in the Asset Hierarchy and deployed to the device, the **FileTransferModule** will be installed on the device.

Accessing the Jobs History via the FileTransferModule

1. Navigate to the **Monitoring** section 2. Select the target device from the device tree 3. Open the **FileTransferModule** 4. Click the **Jobs History** tab {% hint style="info" %} Make sure you have **configured** and **deployed** at least one [File Job](/management-portal/designer/assets/jobs/file-job.md), [FTP Job](/management-portal/designer/assets/jobs/ftp-job.md) or [File Share Job](/management-portal/designer/assets/jobs/file-share-job.md) in an Asset Hierarchy[,](/management-portal/designer/assets/data-connectors/file-share.md) otherwise the FileTransferModule may not be deployed on the device. {% endhint %} *** ### Filtering & Searching in Job Executions From the **Jobs History** page, you can: * **Filter by Job Type** – Show all jobs, only File Jobs, FTP Jobs, or File Share Jobs * **Filter by Time Range** – Limit results to the last 24 hours, last 7 days, or a custom date range * **Search** – Use free-text search to find specific jobs or errors (e.g., search for *Error* or *Timeout*)

Displaying Job Executions (Top Table), and Detailed Job Execution Log (Bottom Table)

### Job Execution List (Top Table) The top table lists all job runs that match your filters, showing: * **State** – Whether the job completed successfully or failed * **Start Time** – When the job started * **Duration** – How long the job took to complete * **Job Name** – The configured name of the job * **Config ID** – The specific data connector used for the job * **Type** – File job, FTP job, or file share job * **Files Transferred** – Number of files moved/copied/deleted in this execution * **MB Transferred** – Total size of transferred data in megabytes * **Device** – The device where the job was executed *** ### Detailed Job Execution Log (Bottom Table) When you select a job from the list, detailed log entries appear in the bottom table.\ These logs show: * Connection attempts and successes * File matching patterns * Download/upload progress * Errors and warnings (if any) *** ### Use Cases The **Jobs History** feature can be used to: * **Validate** that jobs are running on schedule and transferring the expected files. * **Debug** jobs that fail due to connectivity issues, authentication errors, or file matching problems * **Audit** historical transfer data for troubleshooting and compliance purposes --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tricloudnexus.io/management-portal/operations/monitoring/module-details/jobs-history.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.