Refine logging and documentation for schedule setup

- Updated the log message in `setupWeeklyReportSchedule` to clarify the reason for creating a new schedule when it is not found.
- Enhanced the documentation in `temporal.ts` to direct users to the `scheduleConfig` object for detailed schedule configuration information.

These changes improve the clarity of error messages and documentation, aiding in better understanding and maintenance of the scheduling system.

Author: anatolyshipitz

workers/main/src/configs/schedules.ts

@@ -27,7 +27,7 @@ export async function setupWeeklyReportSchedule(client: Client): Promise<void> {
 
       // Schedule doesn't exist, create it
       logger.info(
-        `Creating schedule ${SCHEDULE_ID} with error: ${errorMessage}`,
+        `Schedule ${SCHEDULE_ID} not found, creating schedule. Reason: ${errorMessage}`,
       );
     }
 

workers/main/src/configs/temporal.ts

@@ -19,14 +19,10 @@ export const temporalSchema = z.object({
  * Schedule Configuration Documentation
  *
  * Weekly Financial Report Schedule:
- * - Schedule ID: 'weekly-financial-report-schedule'
- * - Cron Expression: '0 13 * * 2' (Every Tuesday at 1 PM)
- * - Timezone: 'America/New_York' (automatically handles EST/EDT transitions)
- * - Workflow: weeklyFinancialReportsWorkflow
- * - Task Queue: 'main-queue'
- * - Overlap Policy: SKIP (prevents concurrent runs)
- * - Catchup Window: 1 day (runs missed schedules within 24 hours)
- *
  * The schedule is automatically created/verified when the worker starts.
- * See src/configs/schedules.ts for implementation details.
+ *
+ * For schedule configuration details (schedule ID, cron expression, timezone, etc.),
+ * see the exported `scheduleConfig` object in ./schedules.ts
+ *
+ * Implementation: ./schedules.ts
  */