Search the Community
Showing results for tags 'offline'.
Found 2 results
I asked this question before but haven't gotten a response, so I'd like to rephrase it a bit: How does ftrack intend for artists to work when we're offline and can't connect to ftrack? Is there something already in place that I don't know about? The reason I ask is because when something goes wrong in the pipeline and we're unable to connect to ftrack, we're unable to work. Ideally we'd be able to continue working on our local server- managing assets, publishing assets, importing assets, creating tasks, opening tasks, etc. It would all still work. When the connection is returned, ftrack would grab all that data and send it to the cloud where we could start to leverage the website again.
Hello, Last week we lost our connection to ftrack and it required action on ftrack's part to fix (server restart). A huge wrench was thrown into our production because we temporarily lost all of that vital data to drive our pipeline (folder structures, time data, publishes, custom attributes, etc). We outsourced some modifications to our ftrack a while back, so I'm not exactly sure what a normal install of ftrack is capable of, but I'm wondering if there's a system in place that will keep production on track if we lose connection again? One solution I can think of is to have a local application to launch projects from (is ftrack connect capable of that?). So it would basically be what the website is, but it would work with or without an internet connection. Maybe it tries to sync online data once a day, every few hours, or every time you open a file. Basically, we don't want to stop working because we can't connect to the server.