ArcGIS Notebook on AGOL: nvalid value for executionTimeoutInMinutes for notebook job run

[SFM_TravisBott]

New issues since recent AGOL update: all of my scheduled notebooks fails with the message below:

{
  "error": {
    "code": 90031,
    "message": "Invalid value for executionTimeoutInMinutes for notebook job run.",
    "messageCode": "NBO_90031",
    "details": []
  }
}

All of them were set to the maximum allowable limit (1440 minutes, which is 24 hours), and they worked like this for a long time. I since backed them off to 1000, just to be sure, as none of them take remotely that long. Same issue.

So what's the deal? All scripts run fine when executed manually. All are in runtime 10 or 11. How do I get the task to accept a parameter that is entirely within the specified limits?

[LWWCGIS]

We are having the same issue. Notebooks have been failing since Oct. 29

[Sasha_Helton]

Same issue over here. Also close to same starting date, our task run has been consistently successful for years at this point but started failing Oct. 28. Task was disabled for failing each night since then.

[Sasha_Helton]

Talked to Esri support. It's a Bug and they gave the following workaround:

The temporary workaround for the above bug is to set the "maximum minutes" to 1425. Once the bug is resolved, you should be able to set the maximum run time back to the default value of 1440. 

This worked for my tasks and a few of my colleagues' tasks during last nights' run, sounds like doing this didn't help OP so ymmv. 

[mattmerc]

Also seeing the same issue! It looks like it is just the scheduler since the notebooks seem to run fine outside of the scheduler. 

[naanxstop]

Also having the same issue. Glad i'm not alone. Manual run is working good though!

[Geogeek_dev]

This issue has been affecting my scheduled tasks runs as well, starting from the 29th of October and continuing since then.

[LWWCGIS]

I updated a notebook runtime to standard 12 yesterday, reactivated it, and it actually ran on its own this morning.

[Paco_VanSistine]

My script Tasks seem to have 'Succeeded' since 9:15pm yesterday and again today.  *see ESRI post regarding a recent fix/update.

[SFM_TravisBott]

Mine have spontaneously resolved and begun running as normal again. I'd consider this resolved, though I'd like someone to tell me what happened.