Sorry I feel like I am asking a lot of questions b...
# troubleshooting
d
Sorry I feel like I am asking a lot of questions but here we go: I am having an issue after adding a schedule to meltano from one tap-postgres to loader-snowflake. I have tried creating that schedule via the command line’s meltano schedule
meltano schedule add staging2 --extractor tap-postgres--staging2 --loader target-snowflake--staging2 --interval="0 * * * *"
Via command lines meltano job
meltano job add tap-postgres--staging2-to-target-snowflake--staging2 --tasks "[tap-postgres--staging2 target-snowflake--staging2]"
meltano schedule add daily-schedule-tap-postgres--staging2-to-target-snowflake--staging2 --job tap-postgres--staging2-to-target-snowflake--staging2 --interval '@hourly'
And via the UI (screenshot 1) When then starting up the ui, i am getting an error with the output
AttributeError: 'dict' object has no attribute 'job'
It probably helps if i give the output of
meltano schedule list --format=json
which is
Copy code
{
  "schedules": {
    "job": [],
    "elt": [
      {
        "name": "staging2",
        "extractor": "tap-postgres--staging2",
        "loader": "target-snowflake--staging2",
        "transform": "skip",
        "interval": "@hourly",
        "start_date": "2022-06-14",
        "env": {},
        "cron_interval": "0 * * * *",
        "last_successful_run_ended_at": null,
        "elt_args": [
          "tap-postgres--staging2",
          "target-snowflake--staging2",
          "--transform=skip",
          "--state-id=staging2"
        ]
      }
    ]
  }
}
t
I'm having the same issue but it looks like it was a bug in meltano 2.0 and got fixed https://github.com/meltano/meltano/pull/6174
d
Are you still having the issue? I did upgrade to 2.0.1 and still having it
t
yes, it's happening on 2.0.1. A new package hasn't been released yet looks like, even though the fix was merged
Thanks for your patience.
@TomasB and @devon_seitz - Can you check if this latest release resolves your issue?
d
All good @aaronsteers everything seems to checkout! ty!!
t
The pipeline shows in the UI for me but when I try to run the pipeline, it's stuck and I get the below error
Copy code
2022-06-15T14:04:31.879525Z [error    ] Exception on /api/v1/orchestrations/jobs/state [POST] 
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.8/site-packages/flask_restful/__init__.py", line 271, in error_router
    return original_handler(e)
  File "/usr/local/lib/python3.8/site-packages/flask_restful/__init__.py", line 271, in error_router
    return original_handler(e)
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.8/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/lib/python3.8/site-packages/meltano/api/controllers/orchestrations.py", line 207, in job_state
    state_ids = poll_payload["state_ids"]
KeyError: 'state_ids'
2022-06-15T14:04:31.879843Z [info     ] Error: 500 Internal Server Error: The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
d
I haven’t tried running the pipeline yet, ill try it in a little
Circling back here, getting the same error now
KeyError: 'state_ids'
when attempting to run the pipeline
e
@aaronsteers this might be related to https://github.com/meltano/meltano/pull/6009
f
yea, thats actually triggering a bug in a different but related code path than was fixed (listings).
@devon_seitz @edgar_ramirez_mondragon I'll pop an issue for us, i think the that exception is just a side effect not the direct cause (site_ids is missing from the request payload, and why thats missing is probably the actual issue).
d
ty @florian.hines, i think i can get around it by triggering the schedule via airflow instead of via meltano itself
f
yea it should be limited to the UI/API. The meltano cli should work fine as well if you can access it that way.