Tom Hudson

Hi @MetrogApt32 could you please share answer the questions in the template? We need to know what queries were run to debug

thanks for this @0xMimir - we'll add to our backlog!

@Dav1dF is aware - covering issue elsewhere

@dusvyat Nope no news - not a priority for this sprint

@skoleli Just checking the query you used - could you try the below: select m.date as date, m.total_sum as forecast, m.total_sum_explain from mindsdb.testmodel as m join mydb.transactions_transheader as t where...

TBC if we will do this now, or wait for CREATE FORECASTING MODEL

Moved to community contributors project

@Vishnupriya9943 it looks like you are training the model on `anomaly_1` but have named the table `anomaly` Seems like that could be the cause?

Thanks @Vishnupriya9943. Please could you provide the data you used, so we can debug? CSV is fine

Possibly because of an outdated model? Either way, we should handle the error