Been an Otto user for a couple years. Love it. Trying out the Data API proxy, long-lived key feature. I’ve created the key in OttoFMS and can use it to call my database from Paw or using a cURL call in FileMaker. As long as I continue making calls, it works perfectly.
If I wait >15 minutes from the last call, the next attempt will hang and time out. However, the very next call fires and is successful. In other words, it’s behaving as though it needs to fetch a new key (like the regular Data API), but in this case it’s the same key in OttoFMS and in the auth header.
OttoFMS 4.1.1. The log records a 952 error when this happens.
I’ve tried the obvious step of deleting and creating a new long lived token, but I’m seeing the same behavior.
Hi Todd - We are consistently experiencing the same issue after upgrading to OttoFMS. If we continuously use the API key, we don’t see to run into issues but once the 15 minute time happens, our proxy API call hangs indefinitely and we never receive that record creation within our DB.
I attached a screenshot of the first request which times out then re-initiating that same request successfully.
Thanks for fixing this. I’m hosted on ottomatic.cloud, how should I go about updating? Or is that something I need to request instead, since it’s managed?
You can put in a support ticket for your server through console.ottomatic.cloud or you can send an email to support@ottomatic.cloud with a request to upgrade OttoFMS. The hosting team will take care of it from there!
