Server call error

Flow Classic
1

Hello all. We are currently receiving an error when requesting all of our vessels from an API. When we request just a single vessel using the same API, it works. Does anyone know of a setting/parameter within Novacura that would prevent us from receiving a large amount of data in a call?
image

2

Just in general, if you are requesting one item, in this case vessel, you can use the “GET” type. For lot’s of data, normally API endpoints switch to the “POST” type. There shouldn’t be a Novacura flag/setting/parameter that limits the amount of data (unless it is over let’s say a default of 50Mb - and if your data is just txt, it’d be very hard to hit this limit).

3

We can make the same call in PostMan and using a Shell script and even though it takes about 4-5 minutes to get results, we get results. In Novacura is just throws the error I posted above. Do you or anyone know what the Novacura error means? Is there a list of errors that Novacura has listed somewhere so I know where to look?

4

What version of Novacura Serever are you running?

In general, tasks will timeout around 60s. You would have to chunk the data to stay below that 60s marker. There are also some IIS hacks to implement to get the longer timeouts. Follow this “advice” for longer run times:

  1. Upgrade to >6.14 (I recommend 6.15 as 6.14 and lower are no longer supported)
  2. Adjust the following IIS advanced settings for the Flow Server app pool:
  • Start Mode = AlwaysRunning
  • ProcessModel → Idle Timeout (minutes) = 0
  • Recycling → Regular Time Interval (minutes) = 0
  • Recycling → Specific Times = Add one or two times a day when no workflows are scheduled and flow server has less traffic.
  1. Adjust advanced settings for the Server App (under your site):
  • Preload Enabled = True (if this options isn’t available you need to install a IIS feature called Application Initialization Module
  1. Open web.config for flow server and add the following in the system.webServer section if it doesn’t exist:
<applicationInitialization doAppInitAfterRestart="true" skipManagedModules="false">

<add initializationPage="/" />

</applicationInitialization>
5

We are on 6.14.9.16

i will try the settings you mentioned.

Here’s the error in the error.log:

2024-06-24T14:47:39.5610850-07:00: One or more errors occurred. at at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.get_Result()
at NovaCura.Flow.Connector.Rest.RestApi.Get(RestRequest request)
at DynamicModule.ns.Wrapped_IRestApi_21a7a6598d1643259ad560610b7eb637.<Get_DelegateImplementation>__0(IMethodInvocation inputs, GetNextInterceptionBehaviorDelegate getNext)
InnerException: A task was canceled. at
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.get_Result()
at NovaCura.Flow.Connector.Rest.RestApi.Get(RestRequest request)
at DynamicModule.ns.Wrapped_IRestApi_21a7a6598d1643259ad560610b7eb637.<Get_DelegateImplementation>__0(IMethodInvocation inputs, GetNextInterceptionBehaviorDelegate getNext)

6

Our server had these settings currently.