What to do when Model Studio alerts that time variable does not match the one in the input table?

[alisio_meneses]

Hello there.

A previously running workflow scheduled to execute daily failed today. According to the Environment Manager of SAS Viya 3.5, the problem lies in a job created from a simple one line script that calls the macro 'vf_new_iteration', copied from the Batch API code generated by Model Studio when creating a Forecasting project.

Additionally, the following message is displayed when opening the related Forecasting project from Model Studio: "The specified time variable does not match the time variable in the input table."

Log error messages:

note: NOTE: PROCEDURE HTTP used (Total process time):
note: real time 6.34 seconds
note: cpu time 0.00 seconds
note:
note:
normal: Response status: 500
error: ERROR: An invalid response was received.
error: ERROR: Execution terminated by an %ABORT statement.

I did not spot changes in the input table, so I wonder if this is a case of a 'misleading log message' or something else I might be missing.

Does anybody have tips on how to diagnose what changed?

thank you!

[sbxkoenk · Accepted solution]

Hello,

I think (!) this Error Message ...
happens when a table is unloaded from CAS (for example after a controller restart).
If you load a table and then run the Visual Forecasting (VF) project with batch api it will fail on the data update job.
If you try to open the project in ModelStudio after this it will be "broken" (message "The specified time variable does not match the time variable in the input table").

One way to solve this :
If you reload the table again and open the project in ModelStudio it will ask you if you want to update the data. Click Yes.
After this the pipeline is able to run from batch.

Not sure if there's a way to do this without interacting with the software (I mean without clicking Yes in a pop-up window).
I hope others will chime in.

Koen

[alisio_meneses]

right on the money! unloading and loading the table did the trick. I don't really get it though as I used the same table successfully on another project while testing. Maybe I got confused with the tables. Oh well, thank you very much!