After update to Version 6.12 - Message: "Start date cannot be later than expire date"

Hello,
after update Server from 6.11.1 → 6.11.2 → 6.12 in docker enviroment
I become when i start the container in 6.12 this message in the log

In version 6.11.1 i do not become this messages.

Description

024-09-06T07:47:52.155Z 50 pid=1 hostname=1234567890 name=System msg=Error during workspace sync function=announcementSync

err={“type”:“Error”,“message”:“Start date cannot be later than expire date”,“stack”:"Error: Start date cannot be later than expire date\n

at BannersRaw.createOrUpdate (server/models/raw/Banners.ts:63:10)\n

at server/services/banner/service.ts:35:17\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n

=> awaited here:\n

at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n

at app/cloud/server/functions/syncWorkspace/handleCommsSync.ts:64:2\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n

=> awaited here:\n

at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n

at app/cloud/server/functions/syncWorkspace/announcementSync.ts:101:4\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40"}

2024-09-06T07:47:52.156Z 50 pid=1 hostname=1234567890 name=System msg=Error during workspace sync

err={“type”:“Error”,“message”:“Start date cannot be later than expire date”,“stack”:"Error: Start date cannot be later than expire date\n

at BannersRaw.createOrUpdate (server/models/raw/Banners.ts:63:10)\n

at server/services/banner/service.ts:35:17\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n

=> awaited here:\n

at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n

at app/cloud/server/functions/syncWorkspace/handleCommsSync.ts:64:2\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n

=> awaited here:\n

at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n

at app/cloud/server/functions/syncWorkspace/announcementSync.ts:101:4\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n

=> awaited here:\n

at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n

at app/cloud/server/functions/syncWorkspace/index.ts:16:3\n

at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40"}

Server Setup Information

±--------------------------------------------------------+
| SERVER RUNNING |
±--------------------------------------------------------+
| |
| Rocket.Chat Version: 6.12.0 |
| NodeJS Version: 14.21.3 - x64 |
| MongoDB Version: 7.0.7 |
| MongoDB Engine: wiredTiger |
| Platform: linux |
| Process Port: 3000 |
| Site URL: https://rocketchat.germany.de |
| ReplicaSet OpLog: Enabled |
| Commit Hash: ecff0a61cc |
| Commit Branch: HEAD |
| |
±--------------------------------------------------------+

When i Push the Button “sync license update” then i become the same message.

I have seen this on 6.11.2

Can you open an issue?

Fill out the bug template properly please.

1 Like

Can you open an issue?

Actually I have just seen this.

Why do both? It really isn’t necessary and wastes peoples time.

1 Like

Hello,
Two is better than one :slight_smile:
Don’t make any mistakes and it won’t waste anyone’s time.
On which platform is the error message more efficient?
I will then use the most efficient platform.

Not really, no.

Indeed.

There is no ‘efficiency’.

Probably best to first in the forums or open.rocket.chat and then someone will advise you if it is worth opening a bug.