FAQ on iconik Job management.
All jobs are created by other actions and tasks that are created in iconik. e.g:
- New files found
- File transfers
Jobs are dependant on the resources that they will touch when be executed, so it can depend on what the job was doing, what storage it might have involved, whether an ISG that might be involved is offline or not.
The first step to debugging the job is to make a mental modal of what that job will have to do. For example, transcode jobs will try and read the original file. This depends on that storage being available that the file resides on, the file still being available, and being able to read the file. In addition to that it depends whether the file is in the cloud, it will try cloud transcoders, if it's on-premise the ISG transcoder must be online. Then we work out whether the file can be transcoded - it might be an unsupported format, finally after transcoding it will be pushed to another storage which must be ready and available.
Steps in the job process are shown in the job information, and you can see where it might have failed in the steps.
This usually happens because the job has already been done before and doesn't need doing again.
This is because your user needs to have the role Can Read Jobs.
Jobs are part of the history of operations in iconik. In the future we might start removing very old jobs from the list.