Getting 422 for Time Gen-1

Somyadeep Shrivastava 40 Reputation points Microsoft Employee
2025-10-27T23:05:55.5166667+00:00

Until now API was working fine but I'm getting 422 errors unnecessarily, is this a limit issue?
We are internal team at Microsoft trying to utilize timegen-1, and we keep running into unknown issuesUser's image

> nixtla_validate_api_key()
[1] TRUE
> df <- nixtlar::electricity
> head(df)
  unique_id                  ds     y
1        BE 2016-10-22 00:00:00 70.00
2        BE 2016-10-22 01:00:00 37.10
3        BE 2016-10-22 02:00:00 37.10
4        BE 2016-10-22 03:00:00 44.75
5        BE 2016-10-22 04:00:00 37.10
6        BE 2016-10-22 05:00:00 35.61
> nixtla_client_fcst <- nixtla_client_forecast(df, h = 8, level = c(80,95))
Frequency chosen: h
Error in `httr2::req_perform()`:
! HTTP 422 Unprocessable Entity.
Run `rlang::last_trace()` to see where the err
Azure Machine Learning
0 comments No comments
{count} votes

Answer accepted by question author
  1. Aryan Parashar 2,155 Reputation points Microsoft External Staff Moderator
    2025-10-28T07:22:51.94+00:00

    Hi Somyadeep,
    Currently TimeGEN-1 as a serverless model is not accessible to most of the Azure Customers including me, no matter what format you give it will show error.
    Team is currently trying to fix this.

    Feel free to accept this as an answer.

    Thankyou for reaching out to The Microsoft QNA Portal.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.