jerome Posted March 9, 2018 Report Share Posted March 9, 2018 Hi everyone, We use a cloud instance of our project and regularly our users experience some network error: proxy error, connection timeout etc Usually a retry is enough, but eventually it will stop a process and leave an asset unpublished or not entirely prepped. Have anyone experience issues like this ? Is there a common recipe to try/catch all errors that would be network related from ftrack_api ? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.