T
Twenty•4mo ago
Sebastian

✅ Accounts not syncing [CRON stopped]

Users are complaining that they don't see new companies appearing. This started to happen on version v0.50 in production. I've tried to upgrade our testing instance to v0.52, but that didn't help. Users still can't see new companies in testing on version v0.50. The only repeating error I see in the logs is: 
server-1  | Computing new Datasource for cacheKey: 81faddf5-64e9-4321-aac5-66837683bc11-27 out of 0
server-1  | Exception Captured
server-1  |   { user: undefined, workspace: undefined }
server-1  |   [
server-1  |     FileException [Error]: File not found
server-1  |         at FileController.getFile (/app/packages/twenty-server/dist/src/engine/core-modules/file/controllers/file.controller.js:49:23)
server-1  |         at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
server-1  |       code: 'FILE_NOT_FOUND'
server-1  |     }
server-1  |   ]
server-1  | Computing new Datasource for cacheKey: 81faddf5-64e9-4321-aac5-66837683bc11-27 out of 0
server-1  | Exception Captured
server-1  |   { user: undefined, workspace: undefined }
server-1  |   [
server-1  |     FileException [Error]: File not found
server-1  |         at FileController.getFile (/app/packages/twenty-server/dist/src/engine/core-modules/file/controllers/file.controller.js:49:23)
server-1  |         at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
server-1  |       code: 'FILE_NOT_FOUND'
server-1  |     }
server-1  |   ]
where should I start digging?
13 Replies
Guillaume
Guillaume•4mo ago
If i am correct, this was fixed recently. Could you try upgrading to version 0.54 ?
Sebastian
SebastianOP•4mo ago
could this be related to not syncing? users say only calendar sync works, but not emails. maybe it's something on gmail api side?
Sebastian
SebastianOP•4mo ago
I've upgrade to latest (0.54), but now it doesn't load with this error:

message.txt

Sebastian
SebastianOP•4mo ago
server-1                |         length: 129,
server-1                |         severity: 'ERROR',
server-1                |         code: '42703',
server-1                |         detail: undefined,
server-1                |         hint: undefined,
server-1                |         position: '166',
server-1                |         internalPosition: undefined,
server-1                |         internalQuery: undefined,
server-1                |         where: undefined,
server-1                |         schema: undefined,
server-1                |         table: undefined,
server-1                |         column: undefined,
server-1                |         dataType: undefined,
server-1                |         constraint: undefined,
server-1                |         file: 'parse_relation.c',
server-1                |         line: '3722',
server-1                |         routine: 'errorMissingColumn'
server-1                |       },
server-1                |       length: 129,
server-1                |       severity: 'ERROR',
server-1                |       code: '42703',
server-1                |       detail: undefined,
server-1                |       hint: undefined,
server-1                |       position: '166',
server-1                |       internalPosition: undefined,
server-1                |       internalQuery: undefined,
server-1                |       where: undefined,
server-1                |       schema: undefined,
server-1                |       table: undefined,
server-1                |       column: undefined,
server-1                |       dataType: undefined,
server-1                |       constraint: undefined,
server-1                |       file: 'parse_relation.c',
server-1                |       line: '3722',
server-1                |       routine: 'errorMissingColumn'
server-1                |     }
server-1                |   ]
server-1                |         length: 129,
server-1                |         severity: 'ERROR',
server-1                |         code: '42703',
server-1                |         detail: undefined,
server-1                |         hint: undefined,
server-1                |         position: '166',
server-1                |         internalPosition: undefined,
server-1                |         internalQuery: undefined,
server-1                |         where: undefined,
server-1                |         schema: undefined,
server-1                |         table: undefined,
server-1                |         column: undefined,
server-1                |         dataType: undefined,
server-1                |         constraint: undefined,
server-1                |         file: 'parse_relation.c',
server-1                |         line: '3722',
server-1                |         routine: 'errorMissingColumn'
server-1                |       },
server-1                |       length: 129,
server-1                |       severity: 'ERROR',
server-1                |       code: '42703',
server-1                |       detail: undefined,
server-1                |       hint: undefined,
server-1                |       position: '166',
server-1                |       internalPosition: undefined,
server-1                |       internalQuery: undefined,
server-1                |       where: undefined,
server-1                |       schema: undefined,
server-1                |       table: undefined,
server-1                |       column: undefined,
server-1                |       dataType: undefined,
server-1                |       constraint: undefined,
server-1                |       file: 'parse_relation.c',
server-1                |       line: '3722',
server-1                |       routine: 'errorMissingColumn'
server-1                |     }
server-1                |   ]
Sebastian
SebastianOP•4mo ago
I can see it stopped syncing from emails on after Mar 27th. I have a feeling it might be something with Gmail API, but I'm not sure what and where to look for
No description
Guillaume
Guillaume•4mo ago
i would definitly recommend first to upgrade in order to benefit from all our fixes. Then I would try to dig the worker logs
Sebastian
SebastianOP•4mo ago
yes, I've upgrade gradually to 0.54, but this is the error on 54 I've rolled it back to 0.53 and it works but email sync still doesn't
Guillaume
Guillaume•4mo ago
did you try to reload the worker ? (maybe they are just down)
Sebastian
SebastianOP•4mo ago
what do you mean by reload? whenever I do upgrade I run it with --force-recreate. so the container is restarted in any casee
Guillaume
Guillaume•4mo ago
O i see you use docker containers. I am not familiar with this setup but sometimes cron jobs stops and you may need to manually trigger them again. it's in the doc if you search for "start the corn jobs" yarn command:prod cron:messaging:messages-import yarn command:prod cron:messaging:message-list-fetch yarn command:prod cron:calendar-event-list-fetch yarn command:prod cron:calendar-events-import yarn command:prod cron:messaging:ongoing-stale yarn command:prod cron:ongoing-stale yarn command:prod cron:workflow:automated-cron-trigger
Sebastian
SebastianOP•4mo ago
amazing, thanks! let me try to do that I've started them, let's see if that helps. Also, should I be concerned about this error? 
worker-1  | Exception Captured
worker-1  |   undefined
worker-1  |   [
worker-1  |     EntityMetadataNotFoundError: No metadata for "workflowAutomatedTrigger" was found.
worker-1  |         at WorkspaceDataSource.getMetadata (/app/node_modules/typeorm/data-source/DataSource.js:304:19)
worker-1  |         at WorkspaceEntityManager.getRepositoryKey (/app/packages/twenty-server/dist/src/engine/twenty-orm/entity-manager/workspace-entity-manager.js:77:45)
worker-1  |         at WorkspaceEntityManager.getRepository (/app/packages/twenty-server/dist/src/engine/twenty-orm/entity-manager/workspace-entity-manager.js:22:36)
worker-1  |         at WorkspaceDataSource.getRepository (/app/packages/twenty-server/dist/src/engine/twenty-orm/datasource/workspace.datasource.js:25:29)
worker-1  |         at TwentyORMGlobalManager.getRepositoryForWorkspace (/app/packages/twenty-server/dist/src/engine/twenty-orm/twenty-orm-global.manager.js:35:48)
worker-1  |         at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
worker-1  |         at async CronTriggerCronJob.handle (/app/packages/twenty-server/dist/src/modules/workflow/workflow-trigger/automated-trigger/crons/jobs/cron-trigger.cron.job.js:58:5
6)
worker-1  |         at async descriptor.value (/app/packages/twenty-server/dist/src/engine/core-modules/cron/sentry-cron-monitor.decorator.js:60:24)
worker-1  |         at async MessageQueueExplorer.invokeProcessMethods (/app/packages/twenty-server/dist/src/engine/core-modules/message-queue/message-queue.explorer.js:113:17)
worker-1  |         at async MessageQueueExplorer.handleProcessor (/app/packages/twenty-server/dist/src/engine/core-modules/message-queue/message-queue.explorer.js:106:13)
worker-1  |   ]
worker-1  | Exception Captured
worker-1  |   undefined
worker-1  |   [
worker-1  |     EntityMetadataNotFoundError: No metadata for "workflowAutomatedTrigger" was found.
worker-1  |         at WorkspaceDataSource.getMetadata (/app/node_modules/typeorm/data-source/DataSource.js:304:19)
worker-1  |         at WorkspaceEntityManager.getRepositoryKey (/app/packages/twenty-server/dist/src/engine/twenty-orm/entity-manager/workspace-entity-manager.js:77:45)
worker-1  |         at WorkspaceEntityManager.getRepository (/app/packages/twenty-server/dist/src/engine/twenty-orm/entity-manager/workspace-entity-manager.js:22:36)
worker-1  |         at WorkspaceDataSource.getRepository (/app/packages/twenty-server/dist/src/engine/twenty-orm/datasource/workspace.datasource.js:25:29)
worker-1  |         at TwentyORMGlobalManager.getRepositoryForWorkspace (/app/packages/twenty-server/dist/src/engine/twenty-orm/twenty-orm-global.manager.js:35:48)
worker-1  |         at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
worker-1  |         at async CronTriggerCronJob.handle (/app/packages/twenty-server/dist/src/modules/workflow/workflow-trigger/automated-trigger/crons/jobs/cron-trigger.cron.job.js:58:5
6)
worker-1  |         at async descriptor.value (/app/packages/twenty-server/dist/src/engine/core-modules/cron/sentry-cron-monitor.decorator.js:60:24)
worker-1  |         at async MessageQueueExplorer.invokeProcessMethods (/app/packages/twenty-server/dist/src/engine/core-modules/message-queue/message-queue.explorer.js:113:17)
worker-1  |         at async MessageQueueExplorer.handleProcessor (/app/packages/twenty-server/dist/src/engine/core-modules/message-queue/message-queue.explorer.js:106:13)
worker-1  |   ]
Guillaume
Guillaume•4mo ago
No it’s ok. You can skip this one unless it keeps coming back
Sebastian
SebastianOP•4mo ago
yes, I can see it's repeating. also yesterday after running cron commands today I can see in UI Sync failed ok, it's working fine now. in testing it was the issue with People API not enabled and with production running cron commands solved the issue. thanks!

Did you find this page helpful?