Post econ one liners V2 - job is pending indefinitely

Guidance
1

I am attempting to use an econ-one-liners post request to export a One Liner table for a specific run id. I do not receive any errors when running my code, the job status just stays pending indefinitely. Here is my code:


oneliner_url = "https://api.combocurve.com/v2/exports/econ-one-liners"
oneliner_payload = json.dumps({
  "projectId": "64f9dc0461b7ce670921adc4",
  "scenarioId": "691f7a4f25ee9b72b5877a0e",
  "runId" : "6940188991bb2489ff319543",
  "fileType": "parquet",
  "timeZone": "UTC"
})

oneliner_response = requests.request("POST", oneliner_url, headers=headers, data=oneliner_payload)
oneliner_response.raise_for_status()
oneliner_json_data = json.loads(oneliner_response.text)

oneliner_job_id = oneliner_json_data['jobId']

oneliner_job_url = f"https://api.combocurve.com/v2/exports/econ-one-liners/{oneliner_job_id}"
oneliner_job_payload = {}
oneliner_get_response = requests.request("GET", oneliner_job_url, headers=headers, data=oneliner_job_payload)

oneliner_job_get_json_data = json.loads(oneliner_get_response.text)
print(oneliner_job_get_json_data)

Any ideas on why the status won’t change? The job status does not change, even after a few hours/overnight. I used this workflow on econ-monthly and it worked very well. Hoping to use this or something similar for the one-liner. TIA!

2

I created a ticket to investigate.

1 Like
3

Hi, so I tried hardcoding the job-id instead of passing in the oneliner_job_id variable:

url = "https://api.combocurve.com/v2/exports/econ-one-liners/6983b9701510d88a645c0b62"
oneliner_job_payload = {}
oneliner_get_response = requests.request("GET", url, headers=headers, data=oneliner_job_payload)

For some reason, the status does change to “failed” when I do this. Here is the error I received: ‘error’: ‘Export timed out - no files generated within expected time window’.

4

Hi @bethnew

Thanks for flagging this and for using our API.

We found an issue that was affecting some clients when exporting econ one-liners (V2), and we’ve just pushed a fix. When you get a chance, please try running it again.

Also, just to clarify: if no file is generated within 10 minutes, the job will time out and the API will return a “failed” status. We’ll be updating the endpoint documentation to make that behavior clearer.

Let us know if you run into anything else!

5

Thank you, the fix you all deployed fixed the issue. We are up and running. Thanks again!