Post-Deployment Script "Schedule timed out"

OttoFMS
1

Hey guys,

At some point in the past, OttoFMS started wrapping post-deployment scripts in a temporary script schedule named something like OTTO_Server Script | Post_xKNzd. This has a script timeout of 30 minutes to it, and our post-deployment scripts run way longer (many hours at times). As such, it’s generating errors in the OttoFMS deployment log due to the script running past the 30 minutes.

Claris_FileMaker_Server_Admin_Console
Claris_FileMaker_Server_Admin_Console972×644 65.1 KB

I’m grateful it doesn’t halt the script, but in my view this wrapper shouldn’t have the 30 min timeout at all, since it doesn’t know anything about the actual server script.

Can we Disable that timeout please?

You guys are doing awesome work on this product. A+

1 Like
2

Hey Matt,

Thanks for the report. Looks like we don’t pass through the script timeout all the way to the schedule, I’ll get that fixed in our next version. Thanks!

-Kyle

1 Like
3

Hey @HighPower_Matt ,

This issue is fixed with OttoFMS version 4.7.1! The timeout will now be passed all the way to the FM Script Schedule. Let me know if you have any issues with it going forward.

-Kyle

1 Like