Immich diagram for file processing steps

I

Immich•10/4/25, 10:53 PM

:wave: Hey @Akimbo,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.

References

Container Logs:
```
docker compose logs
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
docker ps -a
```
docs
Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA

I

Immich•10/4/25, 10:53 PM

Checklist

I have...

:blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
:blue_square: read applicable release notes.
:blue_square: reviewed the FAQs for known issues.
:blue_square: reviewed Github for known issues.
:blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
:blue_square: uploaded the relevant information (see below).
:blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

Your docker-compose.yml and .env files.
Logs from all the containers and their status (see above).
All the troubleshooting steps you've tried so far.
Any recent changes you've made to Immich or your system.
Details about your system (both software/OS and hardware).
Details about your storage (filesystems, type of disks, output of commands like
```
fdisk -l
```
```
fdisk -l
```
and
```
df -h
```
```
df -h
```
).
The version of the Immich server, mobile app, and other relevant pieces.
Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the

/close

/close

command, and re-open it later if needed.

S

Sergey Katsubo•10/5/25, 6:33 AM

https://docs.immich.app/developer/architecture#high-level-diagram
I have checked the above but I don't see a diagram for this

Could you clarify - is this about a broken doc page or is this a suggestion to improve/extend the docs?

Btw https://docs.immich.app/administration/jobs-workers#jobs

although not a diagram, just a short description

A

AkimboOP•10/5/25, 7:51 AM

@Sergey Katsubo this would be an improvement/extension to the docs

I read through the jobs page but it's just missing the order - is there a specific order that jobs are run in?

S

Sergey Katsubo•10/5/25, 11:42 AM

Asset is uploaded
Then the first job#1 is AssetExtractMetadata
Upon completion it emits an event AssetMetadataExtracted
That event triggers the next job#2 StorageTemplateMigrationSingle
There is a bunch of handlers when jobs are done: onDone
So when Storage Template job is done, it triggers third job#3 AssetGenerateThumbnails
When Thumbnail generation is done, it triggers the next set of jobs {4, 5, 6} SmartSearch, AssetDetectFaces, AssetEncodeVideo (if relevant) here
And so on. You can search for
```
onDone()
```
onDone()
```
onDone()
```
onDone()
and
```
@OnEvent
```
@OnEvent
```
@OnEvent
```
@OnEvent
.

SSergey Katsubo - Asset is uploaded - Then the first job#1 is [AssetExtractMetadata](https://git...

I

Immich•10/5/25, 11:43 AM

    await this.jobRepository.queue({ name: JobName.AssetExtractMetadata, data: { id: asset.id, source: 'upload' } });

    await this.jobRepository.queue({ name: JobName.AssetExtractMetadata, data: { id: asset.id, source: 'upload' } });

    await this.jobRepository.queue({ name: JobName.AssetExtractMetadata, data: { id: asset.id, source: 'upload' } });

    await this.jobRepository.queue({ name: JobName.AssetExtractMetadata, data: { id: asset.id, source: 'upload' } });

    await this.eventRepository.emit('AssetMetadataExtracted', {

    await this.eventRepository.emit('AssetMetadataExtracted', {

    await this.eventRepository.emit('AssetMetadataExtracted', {

    await this.eventRepository.emit('AssetMetadataExtracted', {

  @OnEvent({ name: 'AssetMetadataExtracted' })
  async onAssetMetadataExtracted({ source, assetId }: ArgOf<'AssetMetadataExtracted'>) {
    await this.jobRepository.queue({ name: JobName.StorageTemplateMigrationSingle, data: { source, id: assetId } });
  }

  @OnEvent({ name: 'AssetMetadataExtracted' })
  async onAssetMetadataExtracted({ source, assetId }: ArgOf<'AssetMetadataExtracted'>) {
    await this.jobRepository.queue({ name: JobName.StorageTemplateMigrationSingle, data: { source, id: assetId } });
  }

  @OnEvent({ name: 'AssetMetadataExtracted' })
  async onAssetMetadataExtracted({ source, assetId }: ArgOf<'AssetMetadataExtracted'>) {
    await this.jobRepository.queue({ name: JobName.StorageTemplateMigrationSingle, data: { source, id: assetId } });
  }

  @OnEvent({ name: 'AssetMetadataExtracted' })
  async onAssetMetadataExtracted({ source, assetId }: ArgOf<'AssetMetadataExtracted'>) {
    await this.jobRepository.queue({ name: JobName.StorageTemplateMigrationSingle, data: { source, id: assetId } });
  }

  private async onDone(item: JobItem) {

  private async onDone(item: JobItem) {

  private async onDone(item: JobItem) {

  private async onDone(item: JobItem) {

      case JobName.StorageTemplateMigrationSingle: {
        if (item.data.source === 'upload' || item.data.source === 'copy') {
          await this.jobRepository.queue({ name: JobName.AssetGenerateThumbnails, data: item.data });
        }
        break;
      }

      case JobName.StorageTemplateMigrationSingle: {
        if (item.data.source === 'upload' || item.data.source === 'copy') {
          await this.jobRepository.queue({ name: JobName.AssetGenerateThumbnails, data: item.data });
        }
        break;
      }

      case JobName.StorageTemplateMigrationSingle: {
        if (item.data.source === 'upload' || item.data.source === 'copy') {
          await this.jobRepository.queue({ name: JobName.AssetGenerateThumbnails, data: item.data });
        }
        break;
      }

      case JobName.StorageTemplateMigrationSingle: {
        if (item.data.source === 'upload' || item.data.source === 'copy') {
          await this.jobRepository.queue({ name: JobName.AssetGenerateThumbnails, data: item.data });
        }
        break;
      }

      case JobName.AssetGenerateThumbnails: {

      case JobName.AssetGenerateThumbnails: {

      case JobName.AssetGenerateThumbnails: {

      case JobName.AssetGenerateThumbnails: {

S

Sergey Katsubo•10/5/25, 11:44 AM

Feel free to create a diagram and PR with docs enhancement. Just ask in #contributing before you start to get confirmation (because the jobs ordering may be viewed as "internals")

A

AkimboOP•10/5/25, 2:16 PM

Oh this is perfect - I'll get a diagram made of this in mermaid

The main reason I ask is because sometimes I get stuck jobs so it's useful to know the ordering for further troubleshooting

S

Sergey Katsubo•10/5/25, 6:30 PM

Btw if you'd like to peek into queues/jobs (managed through BullMQ and persisted in Redis) you can add bullmq UI to your Immich stack, smth like

  bullboard:
    image: venatum/bull-board:latest
    environment:
      REDIS_HOST: redis
      BULL_PREFIX: immich_bull
    ports:
      - "3000:3000"

  bullboard:
    image: venatum/bull-board:latest
    environment:
      REDIS_HOST: redis
      BULL_PREFIX: immich_bull
    ports:
      - "3000:3000"

  bullboard:
    image: venatum/bull-board:latest
    environment:
      REDIS_HOST: redis
      BULL_PREFIX: immich_bull
    ports:
      - "3000:3000"

  bullboard:
    image: venatum/bull-board:latest
    environment:
      REDIS_HOST: redis
      BULL_PREFIX: immich_bull
    ports:
      - "3000:3000"

Immich diagram for file processing steps

References

Checklist

Information

Similar Threads

Similar Threads

References

Checklist

Information

Similar Threads