Reviewing Export Jobs

Export jobs are created each time a usage or operational data export is due to run under an Export schedule or when you run an ad-hoc data export. You can review and check the status of Export jobs at any time, which are listed on the Export jobs page:

Read-off job status:
- Pending
- Running
- Succeeded
- Failed
Filter the list by job status.
Filter the list by specifying a date range by job start date.

This topic explains how to review Export jobs for your data exports, check their status, and follow-up on failed jobs:

Reviewing Export Jobs and Checking Status

To review Export jobs and check their status:

1. Select Data exports:

The Data exports section opens.

2. In the sidebar, select Export jobs:

The Export jobs page opens and lists all the jobs created for your Export schedules and ad-hoc data exports:

For each Export job listed, you can read-off:
- The SOURCE TYPE for the Export job.
- The Export job ID, which you can Copy directly to your clipboard.
- The START DATE and time the export was scheduled to run.
- Whether the job was created for an Export schedule or for an ad-hoc export.
You can open the Details page for an Export schedule using the SCHEDULE hotlink text.

Notes:

Schedule not showing? If you delete an Export Schedule after an Export job has been run for the schedule, then "schedule not found" will show under SCHEDULE.
Follow-up on Failed Export jobs? You can make an API call to retrieve details of failed Export jobs - see the section below for how to do this.

2. Export jobs with any STATUS are listed by default when the page opens. If you want to filter the list, use the Status drop-down:

The page adjusts to show only those Export jobs with the selected STATUS.

3. Export jobs for any START DATE are listed by default when the page opens. Use the Start date popup calendars to define a date range to filter the list to show only those Export jobs with a start date within the date range.

Following-Up on Failed Export Jobs

You can use the List EventResponse API call to query for any events of type dataexport.job.failure.

For example:

GET https://api.m3ter.com/organizations/{orgId}/events?eventName=dataexport.job.failure

The response gives details of the Export job failure event:

1
{
2
    "data": [
3
        {
4
            "id": "3bffe288-f04e-4a6f-8d0b-39c616faxyxy",
5
            "eventName": "dataexport.job.failure",
6
            "eventTime": "2024-10-28T10:02:23.892Z",
7
            "m3terEvent": {
8
                "eventData": {
9
                    "jobId": "dc83dec1-94af-4611-b532-fd778b83xy99",
10
                    "code": "NoSuchBucket",
11
                    "sourceType": "USAGE",
12
                    "startedAt": "2024-10-28T10:02:23.614Z",
13
                    "eventType": "DataExportJobFailure",
14
                    "orgId": "eb4d6f1e-0795-484e-a0b8-3640ca22xyxy",
15
                    "scheduleId": "ed1f2303-87b3-4b43-bc27-0b6d70axyx0xa"
16
                },
17
                "eventTime": "2024-10-28T10:02:23.892Z",
18
                "eventName": "dataexport.job.failure"
19
            }
20
        },
21
...
22
]

Next: Data Export Entity Schema

Reviewing Export Jobs

Reviewing Export Jobs and Checking Status

Following-Up on Failed Export Jobs

Additional Support