Y42 Status
Real-time updates of Y42 issues and outages
Y42 status is Operational
Y42 Orchestration
Publishing
Active Incidents
No active incidents
Recently Resolved Incidents
Users running builds or orchestrations may get confronted with an error saying "The system was unable to run dbt model. Please retry later or get in touch with Y42 support ". This is usually only affecting a single or a few jobs in a build but lead to the result being unfinished, i.e. not up-to-date.
Users have reported that simply re-running the affected DAG helps in the majority of cases.
We are currently examining the root cause of the issue and will keep you updated.
Y42 Outage Survival Guide
Y42 Components
Y42 API
Y42 Git
Y42 Integrations
Y42 Login
Y42 Orchestration
Users running builds or orchestrations may get confronted with an error saying "The system was unable to run dbt model. Please retry later or get in touch with Y42 support ". This is usually only affecting a single or a few jobs in a build but lead to the result being unfinished, i.e. not up-to-date.
Users have reported that simply re-running the affected DAG helps in the majority of cases.
We are currently examining the root cause of the issue and will keep you updated.
Y42 Webapp
Y42 Features
Alerts
Data Exports
Data Tests
Modeling
Publishing
Users running builds or orchestrations may get confronted with an error saying "The system was unable to run dbt model. Please retry later or get in touch with Y42 support ". This is usually only affecting a single or a few jobs in a build but lead to the result being unfinished, i.e. not up-to-date.
Users have reported that simply re-running the affected DAG helps in the majority of cases.
We are currently examining the root cause of the issue and will keep you updated.
