Please address the comments from this code review:
## Overall Comments
- Consider setting an expiration/TTL on the Redis hash entries to avoid stale cronIds accumulating if instances are removed or renamed.
- It may be more robust to explicitly stop or destroy existing cron tasks on startup rather than only relying on the Redis ID check to prevent overlapping jobs.

## Individual Comments

### Comment 1
<location> `src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts:4368` </location>
<code_context>
       const task = cron.schedule('0,30 * * * *', async () => {
+        // Check ID before executing (only if cache is available)
+        const cache = this.chatwootService.getCache();
+        if (cache) {
+          const storedId = await cache.hGet(cronKey, this.instance.name);
+          if (storedId && storedId !== cronId) return;
+        }
         this.chatwootService.syncLostMessages({ instanceName: this.instance.name }, chatwootConfig, prepare);
</code_context>

<issue_to_address>
Returning early in the cron task may mask underlying issues.

Adding a log statement when the task is skipped due to ID mismatch will help with future debugging and monitoring.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
        if (cache) {
          const storedId = await cache.hGet(cronKey, this.instance.name);
          if (storedId && storedId !== cronId) return;
        }
=======
        if (cache) {
          const storedId = await cache.hGet(cronKey, this.instance.name);
          if (storedId && storedId !== cronId) {
            this.logger?.info?.(
              `[ChatwootSyncLostMessages] Skipping cron task for instance "${this.instance.name}" due to ID mismatch (storedId: ${storedId}, cronId: ${cronId})`
            );
            return;
          }
        }
>>>>>>> REPLACE

</suggested_fix>

### Comment 2
<location> `src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts:4362` </location>
<code_context>

+      // Generate ID for this cron task and store in cache
+      const cronId = cuid();
+      const cronKey = `chatwoot:syncLostMessages`;
+      await this.chatwootService.getCache()?.hSet(cronKey, this.instance.name, cronId);
+
</code_context>

<issue_to_address>
Cron key does not include instance name, which may cause collisions.

Since cronKey is a static value, using the same cache across multiple environments or services could result in key collisions. To prevent this, add environment or service-specific identifiers to cronKey.

Suggested implementation:

```typescript
      const env = process.env.NODE_ENV || 'development';
      const cronKey = `chatwoot:syncLostMessages:${env}:${this.instance.name}`;
      await this.chatwootService.getCache()?.hSet(cronKey, this.instance.name, cronId);

```

```typescript
        if (cache) {
          const env = process.env.NODE_ENV || 'development';
          const cronKey = `chatwoot:syncLostMessages:${env}:${this.instance.name}`;
          const storedId = await cache.hGet(cronKey, this.instance.name);

```
</issue_to_address>