Webhook timeout intervals and how to avoid them

Webhook requests sent by FotoWeb SaaS and Fotoware On-Premises have a timeout of 10 seconds.

If a webhook request takes longer than the timeout to complete, then the webhook will be shown as timed out in the webhook log. Note that even if a webhook request has timed out, the webhook request handler may still have completed successfully, which is not reflected in Fotoware's logs.

It is strongly recommended that webhook request handlers return as soon as possible or at least significantly earlier than the timeout. Costly, long-running operations, such as outgoing API requests or other I/O operations, should be avoided or offloaded to background workers.

One practice to avoid long-running operations in webhook request handlers is to insert the webhook event into a queue and then process events from the queue in background workers. Note that when hosting a webhook request handler in a PaaS environment, such as Microsoft Azure, there may already be services for queuing and background processing of events, and using those may be preferable to building a custom architecture. Event processing services like Zapier or Microsoft Azure Logic Apps may also automatically use queuing to avoid request timeouts. For more information, see your platform documentation.