// Collaborative Learning Events (community-based-learning-and-skill-sharing) v1 — Prisma seed
// Synthetic sample data, CC0-1.0. Generated deterministically; re-running the
// generator with the same spec and seed reproduces this file exactly.
//
// Delegates are named after the tables (prisma.events), which assumes models
// mapped to those table names. Rename the delegates if your models differ.
import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

async function main() {
    await prisma.events.createMany({
        data: [
            { id: 1, title: "Discussion Hackathon Showcase", topic: "discussion hackathon", event_date: "2023-12-16", format: "workshop" },
            { id: 2, title: "Showcase", topic: "networking", event_date: "2023-10-12", format: "workshop" },
            { id: 3, title: "Retreat", topic: "summit", event_date: "2023-12-24", format: "webinar" },
            { id: 4, title: "Forum", topic: "collaboration", event_date: "2023-09-22", format: "discussion" },
            { id: 5, title: "Workshop Roundtable Panel", topic: "tutorial", event_date: "2023-09-19", format: "discussion" },
            { id: 6, title: "Roundtable Workshop", topic: "presentation hackathon showcase", event_date: "2023-08-24", format: "webinar" },
            { id: 7, title: "Panel", topic: "collaboration", event_date: "2023-09-05", format: "workshop" },
            { id: 8, title: "Workshop Discussion Retreat", topic: "lecture", event_date: "2023-07-11", format: "workshop" },
            { id: 9, title: "Discussion Training", topic: "meetup", event_date: "2023-01-27", format: "workshop" },
            { id: 10, title: "Course", topic: "bootcamp hackathon", event_date: "2023-04-15", format: "webinar" },
            { id: 11, title: "Discussion Course Retreat", topic: "presentation retreat showcase", event_date: "2023-08-20", format: "webinar" },
            { id: 12, title: "Hackathon Roundtable", topic: "panel showcase", event_date: "2023-09-24", format: "webinar" },
            { id: 13, title: "Retreat Bootcamp", topic: "collaboration workshop seminar", event_date: "2023-09-25", format: "workshop" },
            { id: 14, title: "Symposium Webinar", topic: "lecture conference", event_date: "2023-10-15", format: "webinar" },
            { id: 15, title: "Forum Panel Meetup", topic: "lecture presentation", event_date: "2023-03-13", format: "webinar" },
            { id: 16, title: "Training Hackathon", topic: "conference", event_date: "2023-09-18", format: "workshop" },
            { id: 17, title: "Panel Presentation", topic: "presentation", event_date: "2023-10-06", format: "workshop" },
            { id: 18, title: "Bootcamp Showcase Conference", topic: "networking bootcamp lecture", event_date: "2023-12-02", format: "discussion" },
            { id: 19, title: "Training", topic: "presentation conference training", event_date: "2023-12-12", format: "presentation" },
            { id: 20, title: "Roundtable Retreat", topic: "networking", event_date: "2023-10-04", format: "workshop" },
            { id: 21, title: "Forum Lecture", topic: "seminar panel", event_date: "2023-08-11", format: "webinar" },
            { id: 22, title: "Webinar Training Retreat", topic: "bootcamp discussion networking", event_date: "2023-09-14", format: "workshop" },
            { id: 23, title: "Workshop Webinar Conference", topic: "forum presentation", event_date: "2023-01-30", format: "discussion" },
            { id: 24, title: "Hackathon", topic: "course", event_date: "2023-12-23", format: "webinar" },
            { id: 25, title: "Roundtable Presentation Course", topic: "retreat meetup", event_date: "2023-06-15", format: "webinar" },
            { id: 26, title: "Seminar", topic: "training", event_date: "2023-11-05", format: "workshop" },
            { id: 27, title: "Bootcamp", topic: "collaboration", event_date: "2023-07-08", format: "workshop" },
            { id: 28, title: "Training", topic: "presentation", event_date: "2023-10-04", format: "discussion" },
            { id: 29, title: "Bootcamp Panel", topic: "expo panel bootcamp", event_date: "2023-12-19", format: "webinar" },
            { id: 30, title: "Hackathon Expo Meetup", topic: "seminar bootcamp", event_date: "2023-02-04", format: "workshop" },
            { id: 31, title: "Lecture Bootcamp", topic: "forum networking discussion", event_date: "2023-01-19", format: "workshop" },
            { id: 32, title: "Roundtable", topic: "presentation networking", event_date: "2023-02-08", format: "workshop" },
            { id: 33, title: "Workshop", topic: "showcase conference webinar", event_date: "2023-12-06", format: "presentation" },
            { id: 34, title: "Webinar Lecture", topic: "retreat lecture meetup", event_date: "2023-03-22", format: "workshop" },
            { id: 35, title: "Training Bootcamp", topic: "expo collaboration summit", event_date: "2023-05-06", format: "workshop" },
            { id: 36, title: "Meetup Seminar Summit", topic: "collaboration", event_date: "2023-03-10", format: "discussion" },
            { id: 37, title: "Webinar", topic: "seminar discussion", event_date: "2023-07-23", format: "workshop" },
            { id: 38, title: "Bootcamp Conference Presentation", topic: "course webinar", event_date: "2023-08-26", format: "workshop" },
            { id: 39, title: "Conference", topic: "showcase", event_date: "2023-12-17", format: "workshop" },
            { id: 40, title: "Presentation Conference Webinar", topic: "bootcamp", event_date: "2023-05-08", format: "webinar" },
            { id: 41, title: "Workshop Summit", topic: "panel conference", event_date: "2023-12-16", format: "webinar" },
            { id: 42, title: "Discussion Roundtable", topic: "showcase", event_date: "2023-10-21", format: "workshop" },
            { id: 43, title: "Webinar", topic: "showcase", event_date: "2023-11-02", format: "discussion" },
            { id: 44, title: "Meetup Forum", topic: "summit course tutorial", event_date: "2023-08-17", format: "workshop" },
            { id: 45, title: "Conference Hackathon", topic: "hackathon webinar retreat", event_date: "2023-11-21", format: "workshop" },
            { id: 46, title: "Roundtable", topic: "discussion conference", event_date: "2023-11-10", format: "webinar" },
            { id: 47, title: "Symposium", topic: "webinar bootcamp tutorial", event_date: "2023-10-22", format: "discussion" },
            { id: 48, title: "Showcase", topic: "networking webinar", event_date: "2023-01-30", format: "webinar" },
            { id: 49, title: "Showcase Symposium", topic: "lecture expo course", event_date: "2023-04-27", format: "discussion" },
            { id: 50, title: "Conference Presentation Webinar", topic: "presentation tutorial", event_date: "2023-09-04", format: "webinar" },
            { id: 51, title: "Training Symposium", topic: "course collaboration", event_date: "2023-02-18", format: "discussion" },
            { id: 52, title: "Workshop Webinar Training", topic: "training networking hackathon", event_date: "2023-01-11", format: "workshop" },
            { id: 53, title: "Panel Workshop", topic: "course showcase", event_date: "2023-06-24", format: "workshop" },
            { id: 54, title: "Lecture", topic: "presentation panel hackathon", event_date: "2023-11-12", format: "workshop" },
            { id: 55, title: "Workshop Presentation Roundtable", topic: "collaboration tutorial seminar", event_date: "2023-10-13", format: "workshop" },
            { id: 56, title: "Discussion Webinar Seminar", topic: "discussion", event_date: "2023-07-19", format: "workshop" },
            { id: 57, title: "Presentation Retreat", topic: "expo networking workshop", event_date: "2023-07-19", format: "webinar" },
            { id: 58, title: "Workshop Panel Seminar", topic: "forum summit", event_date: "2023-03-23", format: "workshop" },
            { id: 59, title: "Training Meetup Presentation", topic: "summit", event_date: "2023-06-27", format: "workshop" },
            { id: 60, title: "Meetup Forum", topic: "workshop hackathon", event_date: "2023-11-01", format: "workshop" },
            { id: 61, title: "Webinar Presentation Expo", topic: "hackathon workshop", event_date: "2023-10-13", format: "workshop" },
            { id: 62, title: "Expo Showcase", topic: "expo collaboration forum", event_date: "2023-09-22", format: "workshop" },
            { id: 63, title: "Course Workshop", topic: "training", event_date: "2023-05-30", format: "presentation" },
            { id: 64, title: "Webinar Seminar Showcase", topic: "lecture showcase", event_date: "2023-01-28", format: "workshop" },
            { id: 65, title: "Course Summit", topic: "expo meetup bootcamp", event_date: "2023-08-25", format: "workshop" },
            { id: 66, title: "Course", topic: "bootcamp training", event_date: "2023-01-21", format: "webinar" },
            { id: 67, title: "Summit", topic: "retreat webinar workshop", event_date: "2023-09-21", format: "presentation" },
            { id: 68, title: "Lecture Presentation", topic: "meetup", event_date: "2023-06-18", format: "discussion" },
            { id: 69, title: "Bootcamp", topic: "lecture forum", event_date: "2023-02-01", format: "discussion" },
            { id: 70, title: "Training", topic: "training networking panel", event_date: "2023-02-03", format: "webinar" },
            { id: 71, title: "Course", topic: "training", event_date: "2023-10-06", format: "workshop" },
            { id: 72, title: "Training", topic: "summit conference", event_date: "2023-02-20", format: "webinar" },
            { id: 73, title: "Discussion", topic: "bootcamp forum", event_date: "2023-03-16", format: "workshop" },
            { id: 74, title: "Summit Meetup", topic: "expo discussion", event_date: "2023-05-25", format: "webinar" },
            { id: 75, title: "Workshop", topic: "hackathon meetup", event_date: "2023-08-24", format: "workshop" },
            { id: 76, title: "Webinar", topic: "seminar", event_date: "2023-10-11", format: "webinar" },
            { id: 77, title: "Conference", topic: "discussion", event_date: "2023-08-03", format: "webinar" },
            { id: 78, title: "Bootcamp Hackathon", topic: "hackathon", event_date: "2023-12-31", format: "discussion" },
            { id: 79, title: "Showcase", topic: "summit lecture", event_date: "2023-09-30", format: "workshop" },
            { id: 80, title: "Hackathon Summit Retreat", topic: "forum", event_date: "2023-10-28", format: "workshop" },
            { id: 81, title: "Meetup Roundtable", topic: "networking workshop", event_date: "2023-12-04", format: "workshop" },
            { id: 82, title: "Conference Bootcamp Showcase", topic: "conference showcase", event_date: "2023-03-26", format: "discussion" },
            { id: 83, title: "Training", topic: "training presentation", event_date: "2023-10-03", format: "workshop" },
            { id: 84, title: "Hackathon Seminar Roundtable", topic: "discussion", event_date: "2023-11-17", format: "workshop" },
            { id: 85, title: "Meetup Retreat Discussion", topic: "lecture", event_date: "2023-04-27", format: "discussion" },
            { id: 86, title: "Lecture Presentation", topic: "course retreat", event_date: "2023-05-20", format: "workshop" },
            { id: 87, title: "Summit Webinar", topic: "retreat conference workshop", event_date: "2023-03-21", format: "workshop" },
            { id: 88, title: "Seminar Discussion Retreat", topic: "meetup workshop", event_date: "2023-07-29", format: "workshop" },
            { id: 89, title: "Conference Expo Roundtable", topic: "panel", event_date: "2023-12-26", format: "discussion" },
            { id: 90, title: "Showcase Hackathon Forum", topic: "collaboration", event_date: "2023-01-13", format: "workshop" },
            { id: 91, title: "Panel Presentation Workshop", topic: "meetup forum", event_date: "2023-08-15", format: "webinar" },
            { id: 92, title: "Forum", topic: "tutorial training expo", event_date: "2023-11-08", format: "workshop" },
            { id: 93, title: "Discussion Roundtable Bootcamp", topic: "bootcamp expo", event_date: "2023-11-03", format: "workshop" },
            { id: 94, title: "Conference Showcase", topic: "panel showcase", event_date: "2023-09-17", format: "presentation" },
            { id: 95, title: "Workshop", topic: "networking conference", event_date: "2023-09-30", format: "discussion" },
            { id: 96, title: "Expo Showcase Bootcamp", topic: "webinar collaboration forum", event_date: "2023-07-30", format: "webinar" },
            { id: 97, title: "Webinar Panel", topic: "panel forum", event_date: "2023-02-01", format: "webinar" },
            { id: 98, title: "Retreat", topic: "networking presentation training", event_date: "2023-12-28", format: "workshop" },
            { id: 99, title: "Roundtable Symposium", topic: "bootcamp", event_date: "2023-02-10", format: "workshop" },
            { id: 100, title: "Summit", topic: "lecture retreat", event_date: "2023-08-20", format: "workshop" },
        ],
    });
    await prisma.users.createMany({
        data: [
            { id: 1, full_name: "Laura Kumar", email: "laura.kumar@example.com", interests: "business", connections: null },
            { id: 2, full_name: "Laura Johnson", email: "laura.johnson@example.org", interests: "language science", connections: 1 },
            { id: 3, full_name: "Diego Costa", email: "diego.costa@example.com", interests: "literature", connections: 1 },
            { id: 4, full_name: "Chen Smith", email: "chen.smith@example.net", interests: "finance business", connections: 1 },
            { id: 5, full_name: "Sara Wagner", email: "sara.wagner@example.com", interests: "philosophy design", connections: 1 },
            { id: 6, full_name: "Mateo Taylor", email: "mateo.taylor@example.com", interests: "marketing business", connections: 3 },
            { id: 7, full_name: "Mei Castro", email: "mei.castro@example.org", interests: "marketing history", connections: 3 },
            { id: 8, full_name: "Maja Silva", email: "maja.silva@example.net", interests: "art history technology", connections: 2 },
            { id: 9, full_name: "Elena Becker", email: "elena.becker@example.net", interests: "finance psychology math", connections: 8 },
            { id: 10, full_name: "Theo Ruiz", email: "theo.ruiz@example.net", interests: "design", connections: 2 },
            { id: 11, full_name: "Mei Flores", email: "mei.flores@example.net", interests: "coding math science", connections: 4 },
            { id: 12, full_name: "Isaac Nakamura", email: "isaac.nakamura@example.org", interests: "art data", connections: 3 },
            { id: 13, full_name: "Leo Garcia", email: "leo.garcia@example.net", interests: "psychology", connections: 3 },
            { id: 14, full_name: "Karim Ahmed", email: "karim.ahmed@example.net", interests: "finance health data", connections: 13 },
            { id: 15, full_name: "Andre Evans", email: "andre.evans@example.net", interests: "history", connections: 1 },
            { id: 16, full_name: "Mila Torres", email: "mila.torres@example.org", interests: "health business design", connections: 15 },
            { id: 17, full_name: "Chloe Bennett", email: "chloe.bennett@example.net", interests: "business finance psychology", connections: null },
            { id: 18, full_name: "Ibrahim Brown", email: "ibrahim.brown@example.net", interests: "language", connections: 1 },
            { id: 19, full_name: "Maja Nakamura", email: "maja.nakamura@example.org", interests: "data", connections: 13 },
            { id: 20, full_name: "Felix Silva", email: "felix.silva@example.net", interests: "philosophy", connections: 4 },
            { id: 21, full_name: "Chen Ahmed", email: "chen.ahmed@example.org", interests: "finance music", connections: 10 },
            { id: 22, full_name: "Maja Gupta", email: "maja.gupta@example.org", interests: "health history marketing", connections: 3 },
            { id: 23, full_name: "Pedro Patel", email: "pedro.patel@example.com", interests: "music", connections: 3 },
            { id: 24, full_name: "Felix Evans", email: "felix.evans@example.org", interests: "language", connections: 7 },
            { id: 25, full_name: "Alice Hoffmann", email: "alice.hoffmann@example.org", interests: "art design", connections: 2 },
            { id: 26, full_name: "Yusuf Weber", email: "yusuf.weber@example.org", interests: "photography language", connections: 11 },
            { id: 27, full_name: "Ibrahim Ruiz", email: "ibrahim.ruiz@example.net", interests: "photography", connections: 9 },
            { id: 28, full_name: "Chen Nguyen", email: "chen.nguyen@example.net", interests: "business", connections: 3 },
            { id: 29, full_name: "Amir Ahmed", email: "amir.ahmed@example.org", interests: "business photography math", connections: 27 },
            { id: 30, full_name: "Nadia Bennett", email: "nadia.bennett@example.com", interests: "language literature coding", connections: 1 },
            { id: 31, full_name: "Lina Brown", email: "lina.brown@example.com", interests: "marketing finance", connections: 6 },
            { id: 32, full_name: "Carlos Wilson", email: "carlos.wilson@example.com", interests: "history health", connections: 18 },
            { id: 33, full_name: "Arjun Smith", email: "arjun.smith@example.net", interests: "engineering photography", connections: 18 },
            { id: 34, full_name: "Diego Novak", email: "diego.novak@example.org", interests: "literature language writing", connections: 14 },
            { id: 35, full_name: "Jade Park", email: "jade.park@example.net", interests: "science psychology business", connections: 31 },
            { id: 36, full_name: "Jade Ibrahim", email: "jade.ibrahim@example.net", interests: "data", connections: 10 },
            { id: 37, full_name: "Amir Hughes", email: "amir.hughes@example.org", interests: "engineering", connections: 14 },
            { id: 38, full_name: "Nadia Singh", email: "nadia.singh@example.com", interests: "technology", connections: 21 },
            { id: 39, full_name: "Yusuf Vargas", email: "yusuf.vargas@example.net", interests: "writing marketing", connections: null },
            { id: 40, full_name: "Leo Walker", email: "leo.walker@example.org", interests: "health", connections: 22 },
            { id: 41, full_name: "Sofia Schneider", email: "sofia.schneider@example.com", interests: "sports", connections: 20 },
            { id: 42, full_name: "Marco Khan", email: "marco.khan@example.com", interests: "science writing", connections: 21 },
            { id: 43, full_name: "Ravi Almeida", email: "ravi.almeida@example.org", interests: "data engineering", connections: 32 },
            { id: 44, full_name: "Oscar Castro", email: "oscar.castro@example.org", interests: "engineering", connections: 27 },
            { id: 45, full_name: "Amir Miller", email: "amir.miller@example.org", interests: "music science finance", connections: 23 },
            { id: 46, full_name: "Mei Novak", email: "mei.novak@example.net", interests: "music finance", connections: 18 },
            { id: 47, full_name: "Anna Oliveira", email: "anna.oliveira@example.net", interests: "writing history psychology", connections: 4 },
            { id: 48, full_name: "Mila Murphy", email: "mila.murphy@example.net", interests: "sports", connections: 35 },
            { id: 49, full_name: "Noah Schmidt", email: "noah.schmidt@example.org", interests: "coding", connections: 18 },
            { id: 50, full_name: "Jade Yilmaz", email: "jade.yilmaz@example.com", interests: "business art science", connections: 8 },
            { id: 51, full_name: "Nour Reyes", email: "nour.reyes@example.org", interests: "language sports data", connections: 50 },
            { id: 52, full_name: "Karim Baker", email: "karim.baker@example.net", interests: "sports engineering business", connections: null },
            { id: 53, full_name: "Noah Chen", email: "noah.chen@example.com", interests: "history", connections: 16 },
            { id: 54, full_name: "Kai Miller", email: "kai.miller@example.org", interests: "music", connections: 13 },
            { id: 55, full_name: "Carla Ali", email: "carla.ali@example.net", interests: "math technology", connections: 23 },
            { id: 56, full_name: "Pedro Davis", email: "pedro.davis@example.org", interests: "music art", connections: 22 },
            { id: 57, full_name: "Isaac Evans", email: "isaac.evans@example.com", interests: "data writing engineering", connections: 23 },
            { id: 58, full_name: "Mila Bauer", email: "mila.bauer@example.net", interests: "coding design sports", connections: 30 },
            { id: 59, full_name: "Sam Khan", email: "sam.khan@example.org", interests: "psychology technology coding", connections: 16 },
            { id: 60, full_name: "Liam Lee", email: "liam.lee@example.org", interests: "music", connections: null },
            { id: 61, full_name: "Marco Hoffmann", email: "marco.hoffmann@example.com", interests: "philosophy", connections: 45 },
            { id: 62, full_name: "Ben Smith", email: "ben.smith@example.org", interests: "business language technology", connections: 27 },
            { id: 63, full_name: "Mohamed Dubois", email: "mohamed.dubois@example.com", interests: "literature history business", connections: 22 },
            { id: 64, full_name: "Ethan Fischer", email: "ethan.fischer@example.org", interests: "sports technology science", connections: 59 },
            { id: 65, full_name: "Sven Larsen", email: "sven.larsen@example.com", interests: "philosophy coding business", connections: 5 },
            { id: 66, full_name: "Paula Dubois", email: "paula.dubois@example.net", interests: "writing language data", connections: 38 },
            { id: 67, full_name: "Mia Larsen", email: "mia.larsen@example.net", interests: "engineering", connections: 59 },
            { id: 68, full_name: "Nina Reyes", email: "nina.reyes@example.org", interests: "sports writing", connections: 2 },
            { id: 69, full_name: "Zoe Sousa", email: "zoe.sousa@example.org", interests: "design engineering", connections: 56 },
            { id: 70, full_name: "Rosa Vargas", email: "rosa.vargas@example.net", interests: "art", connections: 48 },
            { id: 71, full_name: "Deniz Silva", email: "deniz.silva@example.org", interests: "business", connections: 23 },
            { id: 72, full_name: "Jack Wright", email: "jack.wright@example.com", interests: "technology marketing", connections: 29 },
            { id: 73, full_name: "Rosa Hughes", email: "rosa.hughes@example.com", interests: "sports philosophy technology", connections: null },
            { id: 74, full_name: "Nour Oliveira", email: "nour.oliveira@example.com", interests: "data coding", connections: 37 },
            { id: 75, full_name: "Hana Sousa", email: "hana.sousa@example.org", interests: "coding business", connections: 8 },
            { id: 76, full_name: "Elif Ibrahim", email: "elif.ibrahim@example.org", interests: "marketing photography writing", connections: 21 },
            { id: 77, full_name: "Maya Torres", email: "maya.torres@example.net", interests: "music technology", connections: 33 },
            { id: 78, full_name: "Hana Demir", email: "hana.demir@example.com", interests: "science", connections: 16 },
            { id: 79, full_name: "Lucas Gomez", email: "lucas.gomez@example.com", interests: "history", connections: 20 },
            { id: 80, full_name: "Theo Becker", email: "theo.becker@example.net", interests: "marketing data", connections: null },
            { id: 81, full_name: "Lena Schneider", email: "lena.schneider@example.com", interests: "engineering", connections: 68 },
            { id: 82, full_name: "Alice Almeida", email: "alice.almeida@example.org", interests: "writing engineering", connections: 65 },
            { id: 83, full_name: "Kai Kumar", email: "kai.kumar@example.org", interests: "science engineering writing", connections: 42 },
            { id: 84, full_name: "Hugo Rossi", email: "hugo.rossi@example.com", interests: "writing coding", connections: 59 },
            { id: 85, full_name: "Jade Jansen", email: "jade.jansen@example.net", interests: "coding", connections: 12 },
            { id: 86, full_name: "Emma Jensen", email: "emma.jensen@example.net", interests: "business", connections: 7 },
            { id: 87, full_name: "Elena Diaz", email: "elena.diaz@example.org", interests: "history", connections: null },
            { id: 88, full_name: "Uma Wilson", email: "uma.wilson@example.org", interests: "business health", connections: 21 },
            { id: 89, full_name: "Priya Ali", email: "priya.ali@example.com", interests: "literature science design", connections: 45 },
            { id: 90, full_name: "Elif Becker", email: "elif.becker@example.com", interests: "history marketing", connections: 3 },
            { id: 91, full_name: "Theo Martin", email: "theo.martin@example.com", interests: "marketing math", connections: 26 },
            { id: 92, full_name: "Uma Ali", email: "uma.ali@example.org", interests: "business", connections: 76 },
            { id: 93, full_name: "Yara Park", email: "yara.park@example.net", interests: "health history marketing", connections: null },
            { id: 94, full_name: "Jack Oliveira", email: "jack.oliveira@example.org", interests: "language writing music", connections: 12 },
            { id: 95, full_name: "Olivia Park", email: "olivia.park@example.com", interests: "history", connections: 7 },
            { id: 96, full_name: "Maja Rossi", email: "maja.rossi@example.com", interests: "history marketing music", connections: 50 },
            { id: 97, full_name: "Lina Torres", email: "lina.torres@example.com", interests: "finance", connections: 70 },
            { id: 98, full_name: "Karim Kaya", email: "karim.kaya@example.net", interests: "business", connections: 84 },
            { id: 99, full_name: "Tomas Hassan", email: "tomas.hassan@example.com", interests: "health photography marketing", connections: 16 },
            { id: 100, full_name: "Rafael Nakamura", email: "rafael.nakamura@example.org", interests: "photography literature", connections: 37 },
            { id: 101, full_name: "Julia Meyer", email: "julia.meyer@example.net", interests: "health psychology", connections: 15 },
            { id: 102, full_name: "Rafael Bauer", email: "rafael.bauer@example.com", interests: "coding health engineering", connections: 66 },
            { id: 103, full_name: "Hana Gupta", email: "hana.gupta@example.org", interests: "psychology", connections: 91 },
            { id: 104, full_name: "Emma Gupta", email: "emma.gupta@example.net", interests: "art", connections: 77 },
            { id: 105, full_name: "Selin Kim", email: "selin.kim@example.com", interests: "writing", connections: 71 },
            { id: 106, full_name: "Omar Brown", email: "omar.brown@example.com", interests: "psychology sports", connections: 33 },
            { id: 107, full_name: "Tomas Tanaka", email: "tomas.tanaka@example.com", interests: "health", connections: 13 },
            { id: 108, full_name: "Fatima Davis", email: "fatima.davis@example.com", interests: "writing", connections: 85 },
            { id: 109, full_name: "Laura Singh", email: "laura.singh@example.org", interests: "language music coding", connections: null },
            { id: 110, full_name: "Sofia Schneider", email: "sofia.schneider@example.net", interests: "business marketing", connections: 72 },
            { id: 111, full_name: "Ines Novak", email: "ines.novak@example.org", interests: "business history data", connections: 101 },
            { id: 112, full_name: "Hugo Patel", email: "hugo.patel@example.com", interests: "history art", connections: 26 },
            { id: 113, full_name: "Sofia Almeida", email: "sofia.almeida@example.org", interests: "philosophy marketing engineering", connections: 66 },
            { id: 114, full_name: "Chloe Wright", email: "chloe.wright@example.org", interests: "psychology engineering art", connections: 93 },
            { id: 115, full_name: "Sara Costa", email: "sara.costa@example.com", interests: "photography finance", connections: 64 },
            { id: 116, full_name: "Omar Demir", email: "omar.demir@example.com", interests: "data science", connections: 102 },
            { id: 117, full_name: "Ravi Johnson", email: "ravi.johnson@example.net", interests: "music philosophy technology", connections: 47 },
            { id: 118, full_name: "Sara Kowalski", email: "sara.kowalski@example.net", interests: "literature psychology technology", connections: 16 },
            { id: 119, full_name: "Olivia Shah", email: "olivia.shah@example.org", interests: "music psychology", connections: 28 },
            { id: 120, full_name: "Alice Demir", email: "alice.demir@example.net", interests: "engineering sports marketing", connections: 13 },
            { id: 121, full_name: "Julia Kowalski", email: "julia.kowalski@example.org", interests: "writing philosophy", connections: 117 },
            { id: 122, full_name: "Sara Taylor", email: "sara.taylor@example.com", interests: "coding science", connections: 51 },
            { id: 123, full_name: "Rafael Ibrahim", email: "rafael.ibrahim@example.com", interests: "photography", connections: 87 },
            { id: 124, full_name: "Ines Sousa", email: "ines.sousa@example.net", interests: "psychology sports coding", connections: 64 },
            { id: 125, full_name: "Maja Tanaka", email: "maja.tanaka@example.net", interests: "design", connections: 97 },
            { id: 126, full_name: "Daniel Torres", email: "daniel.torres@example.net", interests: "design writing psychology", connections: 122 },
            { id: 127, full_name: "Anna Silva", email: "anna.silva@example.net", interests: "science", connections: 22 },
            { id: 128, full_name: "Jonas Wang", email: "jonas.wang@example.com", interests: "finance", connections: 11 },
            { id: 129, full_name: "David Zhang", email: "david.zhang@example.com", interests: "literature", connections: 14 },
            { id: 130, full_name: "Lucas Wilson", email: "lucas.wilson@example.org", interests: "data marketing science", connections: 103 },
            { id: 131, full_name: "Zara Hughes", email: "zara.hughes@example.org", interests: "business", connections: null },
            { id: 132, full_name: "Carla Carter", email: "carla.carter@example.com", interests: "health coding", connections: null },
            { id: 133, full_name: "Priya Andersen", email: "priya.andersen@example.org", interests: "photography data literature", connections: 60 },
            { id: 134, full_name: "Elif Singh", email: "elif.singh@example.org", interests: "history science", connections: 79 },
            { id: 135, full_name: "Uma Castro", email: "uma.castro@example.org", interests: "math coding", connections: 122 },
            { id: 136, full_name: "Ana Costa", email: "ana.costa@example.net", interests: "science", connections: 31 },
            { id: 137, full_name: "Sofia Park", email: "sofia.park@example.net", interests: "sports philosophy", connections: null },
            { id: 138, full_name: "Hana Fischer", email: "hana.fischer@example.org", interests: "design photography", connections: 65 },
            { id: 139, full_name: "Isaac Wilson", email: "isaac.wilson@example.org", interests: "music marketing", connections: 25 },
            { id: 140, full_name: "Deniz Wright", email: "deniz.wright@example.net", interests: "sports psychology coding", connections: 28 },
            { id: 141, full_name: "Yusuf Flores", email: "yusuf.flores@example.net", interests: "coding", connections: 140 },
            { id: 142, full_name: "Paula Pereira", email: "paula.pereira@example.org", interests: "writing music engineering", connections: 46 },
            { id: 143, full_name: "Felix Kowalski", email: "felix.kowalski@example.com", interests: "psychology science", connections: 72 },
            { id: 144, full_name: "Hana Flores", email: "hana.flores@example.net", interests: "coding", connections: 78 },
            { id: 145, full_name: "Paula Moreau", email: "paula.moreau@example.org", interests: "business music", connections: 78 },
            { id: 146, full_name: "Ibrahim Schmidt", email: "ibrahim.schmidt@example.org", interests: "philosophy", connections: 95 },
            { id: 147, full_name: "Isaac Sousa", email: "isaac.sousa@example.net", interests: "engineering marketing writing", connections: 6 },
            { id: 148, full_name: "Daniel Jansen", email: "daniel.jansen@example.org", interests: "sports", connections: 18 },
            { id: 149, full_name: "Nadia Adams", email: "nadia.adams@example.com", interests: "science philosophy art", connections: 137 },
            { id: 150, full_name: "Zara Schmidt", email: "zara.schmidt@example.org", interests: "music", connections: 24 },
            { id: 151, full_name: "Grace Young", email: "grace.young@example.net", interests: "engineering", connections: 41 },
            { id: 152, full_name: "Isaac Hughes", email: "isaac.hughes@example.org", interests: "music science", connections: 117 },
            { id: 153, full_name: "Theo Vargas", email: "theo.vargas@example.net", interests: "history literature", connections: 21 },
            { id: 154, full_name: "Tariq Zhang", email: "tariq.zhang@example.net", interests: "data art", connections: 103 },
            { id: 155, full_name: "Theo Smith", email: "theo.smith@example.org", interests: "business technology marketing", connections: 51 },
            { id: 156, full_name: "Selin Schmidt", email: "selin.schmidt@example.net", interests: "marketing psychology health", connections: 78 },
            { id: 157, full_name: "Alice Kim", email: "alice.kim@example.net", interests: "language business", connections: 106 },
            { id: 158, full_name: "Theo Wang", email: "theo.wang@example.com", interests: "finance", connections: 1 },
            { id: 159, full_name: "Yara Hughes", email: "yara.hughes@example.net", interests: "finance marketing", connections: 129 },
            { id: 160, full_name: "Ibrahim Jansen", email: "ibrahim.jansen@example.com", interests: "literature art music", connections: 97 },
            { id: 161, full_name: "Elif Chen", email: "elif.chen@example.com", interests: "finance", connections: 93 },
            { id: 162, full_name: "Sara Klein", email: "sara.klein@example.org", interests: "business data finance", connections: 94 },
            { id: 163, full_name: "Maya Nguyen", email: "maya.nguyen@example.org", interests: "history coding", connections: 69 },
            { id: 164, full_name: "Maya Chen", email: "maya.chen@example.com", interests: "sports psychology", connections: 48 },
            { id: 165, full_name: "Ravi Hughes", email: "ravi.hughes@example.org", interests: "design", connections: 10 },
            { id: 166, full_name: "Jade Zhang", email: "jade.zhang@example.net", interests: "writing", connections: 100 },
            { id: 167, full_name: "Paula Adams", email: "paula.adams@example.org", interests: "science technology engineering", connections: 120 },
            { id: 168, full_name: "Zara Vargas", email: "zara.vargas@example.com", interests: "engineering psychology", connections: 36 },
            { id: 169, full_name: "Mohamed Novak", email: "mohamed.novak@example.net", interests: "history design writing", connections: 57 },
            { id: 170, full_name: "Chloe Lee", email: "chloe.lee@example.com", interests: "business", connections: 96 },
            { id: 171, full_name: "Sofia Schneider", email: "sofia.schneider@example.org", interests: "music data", connections: 86 },
            { id: 172, full_name: "Maria Gomez", email: "maria.gomez@example.org", interests: "coding photography", connections: null },
            { id: 173, full_name: "Karim Sato", email: "karim.sato@example.net", interests: "writing psychology", connections: 129 },
            { id: 174, full_name: "Anna Flores", email: "anna.flores@example.org", interests: "philosophy sports engineering", connections: 69 },
            { id: 175, full_name: "Nina Patel", email: "nina.patel@example.com", interests: "art writing", connections: 68 },
            { id: 176, full_name: "Lucas Hansen", email: "lucas.hansen@example.org", interests: "literature history health", connections: 89 },
            { id: 177, full_name: "Nina Becker", email: "nina.becker@example.net", interests: "language literature philosophy", connections: 160 },
            { id: 178, full_name: "Fatima Fischer", email: "fatima.fischer@example.net", interests: "music photography art", connections: null },
            { id: 179, full_name: "Ruby Becker", email: "ruby.becker@example.org", interests: "photography", connections: 40 },
            { id: 180, full_name: "Jonas Garcia", email: "jonas.garcia@example.com", interests: "data", connections: 125 },
            { id: 181, full_name: "Maja Smith", email: "maja.smith@example.org", interests: "marketing", connections: 45 },
            { id: 182, full_name: "Emma Patel", email: "emma.patel@example.com", interests: "sports", connections: null },
            { id: 183, full_name: "Jack Gupta", email: "jack.gupta@example.com", interests: "engineering writing psychology", connections: 146 },
            { id: 184, full_name: "Ruby Larsen", email: "ruby.larsen@example.net", interests: "business", connections: null },
            { id: 185, full_name: "Chloe Walker", email: "chloe.walker@example.com", interests: "art sports", connections: 178 },
            { id: 186, full_name: "Hana Cruz", email: "hana.cruz@example.org", interests: "photography", connections: null },
            { id: 187, full_name: "Ivan Wagner", email: "ivan.wagner@example.com", interests: "coding technology business", connections: 37 },
            { id: 188, full_name: "Alice Miller", email: "alice.miller@example.net", interests: "psychology math sports", connections: 122 },
            { id: 189, full_name: "James Garcia", email: "james.garcia@example.org", interests: "photography technology", connections: 108 },
            { id: 190, full_name: "Olivia Becker", email: "olivia.becker@example.com", interests: "music philosophy", connections: 7 },
            { id: 191, full_name: "Mia Demir", email: "mia.demir@example.com", interests: "language", connections: 17 },
            { id: 192, full_name: "Laura Chen", email: "laura.chen@example.net", interests: "technology philosophy", connections: 147 },
            { id: 193, full_name: "David Becker", email: "david.becker@example.org", interests: "data", connections: 128 },
            { id: 194, full_name: "Selin Kaya", email: "selin.kaya@example.org", interests: "writing history", connections: 17 },
            { id: 195, full_name: "Amir Bennett", email: "amir.bennett@example.com", interests: "literature writing art", connections: 15 },
            { id: 196, full_name: "Uma Wright", email: "uma.wright@example.net", interests: "psychology", connections: 157 },
            { id: 197, full_name: "Sam Miller", email: "sam.miller@example.net", interests: "design", connections: 167 },
            { id: 198, full_name: "Maja Johnson", email: "maja.johnson@example.com", interests: "math writing", connections: 164 },
            { id: 199, full_name: "Sven Murphy", email: "sven.murphy@example.net", interests: "literature photography philosophy", connections: 106 },
            { id: 200, full_name: "Lina Mendes", email: "lina.mendes@example.net", interests: "marketing music finance", connections: 99 },
        ],
    });
    await prisma.forum_posts.createMany({
        data: [
            { id: 1, user_id: 22, content: "The report was cancelled after a late check. A late follow-up: the invoice was delayed. The shipment was processed after a repeat check. The invoice was rescheduled following a duplicate review.", created_at: new Date("2023-06-23T17:20:44Z"), topic: "feedback innovation skills education learning", likes: 356 },
            { id: 2, user_id: 142, content: "Flagged as duplicate. The account owner completed the account. The report was cancelled following an unusual review.", created_at: new Date("2023-02-17T14:43:30Z"), topic: "collaboration discussion engagement innovation", likes: 768 },
            { id: 3, user_id: 79, content: "The booking was updated — incomplete case, no further action. A duplicate account was delayed the same day. The account was refunded following a duplicate review. The session was refunded after a partial check.", created_at: new Date("2023-09-20T22:04:47Z"), topic: "learning community development discussion", likes: 377 },
            { id: 4, user_id: 111, content: "The reviewer asked for a change and the refund was processed. No response from the reviewer, so the booking was refunded. The supplier reported an urgent issue; the account was confirmed. A partial follow-up: the shipment was resolved.", created_at: new Date("2023-05-20T11:31:50Z"), topic: "learning", likes: 433 },
            { id: 5, user_id: 17, content: "The team asked for a change and the item was escalated. The reviewer reported a routine issue; the document was reopened.", created_at: new Date("2023-07-17T18:51:03Z"), topic: "networking development skills feedback", likes: 647 },
            { id: 6, user_id: 131, content: "A standard request was completed the same day. A late follow-up: the report was closed. The customer asked for a change and the booking was cancelled.", created_at: new Date("2023-06-28T18:32:41Z"), topic: "skills education feedback learning innovation", likes: 710 },
            { id: 7, user_id: 117, content: "An unusual follow-up: the order was rescheduled. Flagged as late. The courier reopened the invoice. The team reported a repeat issue; the item was resolved. The transfer was updated after a routine check.", created_at: new Date("2023-07-14T18:26:56Z"), topic: "networking", likes: 291 },
            { id: 8, user_id: 175, content: "A standard follow-up: the appointment was approved. The invoice was reopened following a late review. Flagged as incomplete. The supplier completed the invoice. The order was escalated — minor case, no further action.", created_at: new Date("2023-01-11T21:36:54Z"), topic: "feedback resources engagement learning community", likes: 307 },
            { id: 9, user_id: 138, content: "The team reported a duplicate issue; the booking was delayed. The reviewer reported an unusual issue; the account was approved.", created_at: new Date("2023-12-08T17:35:20Z"), topic: "engagement collaboration learning", likes: 542 },
            { id: 10, user_id: 136, content: "Flagged as minor. The courier updated the account. No response from the customer, so the appointment was closed. A duplicate follow-up: the invoice was processed.", created_at: new Date("2023-01-14T18:48:53Z"), topic: "development innovation community discussion", likes: 497 },
            { id: 11, user_id: 13, content: "The customer confirmed the details and the refund was closed. An incomplete claim was delayed the same day. The supplier asked for a change and the account was closed.", created_at: new Date("2023-07-19T12:49:09Z"), topic: "engagement community", likes: 242 },
            { id: 12, user_id: 136, content: "The supplier asked for a change and the delivery was resolved. A routine invoice was refunded the same day. The delivery was resolved following a late review.", created_at: new Date("2023-08-08T21:29:12Z"), topic: "feedback development innovation collaboration", likes: 518 },
            { id: 13, user_id: 166, content: "A repeat follow-up: the claim was cancelled. The transfer was delayed after an incomplete check.", created_at: new Date("2023-02-16T16:14:01Z"), topic: "community development education", likes: 525 },
            { id: 14, user_id: 194, content: "The order was processed — repeat case, no further action. The reviewer asked for a change and the session was delayed. Flagged as late. The reviewer reviewed the document. The session was delayed — duplicate case, no further action.", created_at: new Date("2023-10-11T12:15:32Z"), topic: "education resources skills collaboration", likes: 865 },
            { id: 15, user_id: 150, content: "The reviewer confirmed the details and the shipment was approved. The refund was completed — automatic case, no further action.", created_at: new Date("2023-02-11T00:52:15Z"), topic: "development education learning skills", likes: 347 },
            { id: 16, user_id: 179, content: "An incomplete order was escalated the same day. Flagged as standard. Support completed the record. The reviewer asked for a change and the claim was rescheduled.", created_at: new Date("2023-11-05T14:15:19Z"), topic: "innovation education networking learning", likes: 675 },
            { id: 17, user_id: 192, content: "The account owner asked for a change and the booking was resolved. Support reported a minor issue; the record was cancelled. Flagged as minor. The customer closed the claim.", created_at: new Date("2023-08-28T17:31:03Z"), topic: "resources", likes: 446 },
            { id: 18, user_id: 28, content: "An unusual transfer was escalated the same day. The customer reported an urgent issue; the account was completed. No response from the courier, so the session was updated. An urgent refund was cancelled the same day.", created_at: new Date("2023-03-23T01:45:45Z"), topic: "education networking discussion community skills", likes: 591 },
            { id: 19, user_id: 82, content: "A routine item was rejected the same day. The record was delayed after a routine check.", created_at: new Date("2023-08-22T06:31:56Z"), topic: "innovation feedback engagement learning", likes: 641 },
            { id: 20, user_id: 1, content: "The supplier asked for a change and the appointment was refunded. Support reported an unusual issue; the session was approved.", created_at: new Date("2023-04-28T11:10:48Z"), topic: "skills innovation collaboration networking", likes: 462 },
            { id: 21, user_id: 96, content: "An operator confirmed the details and the account was rejected. The report was refunded after a partial check. An automatic follow-up: the appointment was escalated. The payment was completed after a manual check.", created_at: new Date("2023-04-03T13:22:44Z"), topic: "learning community", likes: 496 },
            { id: 22, user_id: 20, content: "A standard shipment was reopened the same day. The item was rejected following a duplicate review. The refund was confirmed following an automatic review.", created_at: new Date("2023-01-19T20:33:19Z"), topic: "resources education learning development innovation", likes: 517 },
            { id: 23, user_id: 168, content: "No response from the reviewer, so the shipment was completed. An automatic follow-up: the claim was reopened. The reviewer reported an automatic issue; the appointment was rescheduled.", created_at: new Date("2023-06-18T08:40:17Z"), topic: "collaboration innovation", likes: 478 },
            { id: 24, user_id: 55, content: "No response from the team, so the transfer was escalated. No response from the customer, so the account was rescheduled. The shipment was cancelled after a minor check. Support asked for a change and the request was processed.", created_at: new Date("2023-09-13T15:58:05Z"), topic: "skills networking discussion feedback engagement", likes: 370 },
            { id: 25, user_id: 199, content: "The team asked for a change and the record was escalated. The session was replaced after a repeat check. Flagged as standard. The account owner completed the session.", created_at: new Date("2023-09-15T21:18:54Z"), topic: "discussion", likes: 627 },
            { id: 26, user_id: 5, content: "The appointment was replaced following a duplicate review. An unusual follow-up: the invoice was reopened. The team confirmed the details and the report was rejected.", created_at: new Date("2023-05-02T21:05:32Z"), topic: "education", likes: 449 },
            { id: 27, user_id: 83, content: "An urgent ticket was refunded the same day. The order was updated following a manual review.", created_at: new Date("2023-02-09T23:13:22Z"), topic: "collaboration innovation development", likes: 226 },
            { id: 28, user_id: 142, content: "No response from the reviewer, so the refund was closed. The customer asked for a change and the delivery was rescheduled.", created_at: new Date("2023-05-15T13:28:02Z"), topic: "collaboration resources community learning", likes: 680 },
            { id: 29, user_id: 161, content: "The courier asked for a change and the booking was refunded. The booking was replaced following an automatic review.", created_at: new Date("2023-03-13T18:13:20Z"), topic: "innovation", likes: 358 },
            { id: 30, user_id: 122, content: "The request was cancelled after a minor check. A minor follow-up: the report was resolved. The invoice was delayed following an unusual review.", created_at: new Date("2023-01-13T20:38:03Z"), topic: "networking skills discussion", likes: 450 },
            { id: 31, user_id: 76, content: "An operator reported an unusual issue; the report was reopened. No response from the reviewer, so the record was refunded. The supplier confirmed the details and the claim was delayed.", created_at: new Date("2023-07-11T14:37:40Z"), topic: "collaboration discussion", likes: 402 },
            { id: 32, user_id: 144, content: "No response from the reviewer, so the item was escalated. The supplier confirmed the details and the order was processed. The supplier asked for a change and the item was processed. The shipment was approved after a partial check.", created_at: new Date("2023-01-24T14:54:03Z"), topic: "skills engagement discussion community", likes: 478 },
            { id: 33, user_id: 100, content: "The account owner confirmed the details and the session was rescheduled. No response from the team, so the refund was refunded.", created_at: new Date("2023-01-15T22:05:19Z"), topic: "engagement development", likes: 652 },
            { id: 34, user_id: 32, content: "An operator reported an automatic issue; the account was rejected. No response from support, so the request was approved. An operator asked for a change and the claim was completed. A standard request was refunded the same day.", created_at: new Date("2023-10-01T13:47:35Z"), topic: "networking discussion", likes: 408 },
            { id: 35, user_id: 121, content: "The report was approved — standard case, no further action. The booking was cancelled — routine case, no further action. An urgent follow-up: the transfer was reopened. The reviewer asked for a change and the item was confirmed.", created_at: new Date("2023-03-03T15:05:16Z"), topic: "learning innovation education development networking", likes: 335 },
            { id: 36, user_id: 13, content: "An urgent transfer was completed the same day. A repeat follow-up: the delivery was processed. No response from support, so the record was completed. The courier reported a standard issue; the item was delayed.", created_at: new Date("2023-02-19T22:41:30Z"), topic: "discussion community education learning", likes: 446 },
            { id: 37, user_id: 101, content: "No response from an operator, so the document was updated. Flagged as urgent. The account owner closed the report.", created_at: new Date("2023-06-14T15:35:40Z"), topic: "resources", likes: 747 },
            { id: 38, user_id: 158, content: "Flagged as standard. The customer reviewed the booking. The shipment was confirmed after an urgent check. No response from the supplier, so the shipment was reopened. The reviewer reported a duplicate issue; the booking was delayed.", created_at: new Date("2023-02-23T08:31:11Z"), topic: "resources innovation", likes: 548 },
            { id: 39, user_id: 77, content: "The shipment was reopened after an automatic check. The reviewer confirmed the details and the booking was escalated.", created_at: new Date("2023-11-13T23:19:49Z"), topic: "education innovation resources learning", likes: 664 },
            { id: 40, user_id: 56, content: "The courier confirmed the details and the refund was completed. Support confirmed the details and the report was confirmed.", created_at: new Date("2023-07-24T21:48:32Z"), topic: "skills innovation engagement", likes: 734 },
            { id: 41, user_id: 100, content: "Flagged as urgent. The courier refunded the request. The account owner reported a repeat issue; the transfer was rescheduled. Flagged as unusual. The team confirmed the record.", created_at: new Date("2023-06-13T16:03:55Z"), topic: "engagement innovation collaboration education", likes: 483 },
            { id: 42, user_id: 115, content: "Flagged as urgent. The reviewer replaced the shipment. The reviewer reported a duplicate issue; the appointment was rejected. An operator confirmed the details and the delivery was processed.", created_at: new Date("2023-04-02T15:04:21Z"), topic: "resources collaboration", likes: 585 },
            { id: 43, user_id: 184, content: "The request was reviewed after an automatic check. The transfer was reviewed after an automatic check. The supplier asked for a change and the order was reopened. The courier confirmed the details and the account was reopened.", created_at: new Date("2023-04-24T08:12:41Z"), topic: "collaboration discussion resources community", likes: 439 },
            { id: 44, user_id: 191, content: "An operator confirmed the details and the record was approved. The reviewer reported a standard issue; the delivery was closed. The customer reported a routine issue; the item was confirmed.", created_at: new Date("2023-01-15T10:01:19Z"), topic: "innovation", likes: 569 },
            { id: 45, user_id: 80, content: "No response from the team, so the account was closed. The account owner reported an automatic issue; the shipment was delayed. The team reported an incomplete issue; the transfer was approved. The transfer was reviewed following a repeat review.", created_at: new Date("2023-06-24T15:58:11Z"), topic: "engagement skills", likes: 396 },
            { id: 46, user_id: 164, content: "Support asked for a change and the session was reopened. The ticket was rescheduled following an incomplete review. The team confirmed the details and the refund was reviewed.", created_at: new Date("2023-01-20T20:11:40Z"), topic: "engagement", likes: 483 },
            { id: 47, user_id: 96, content: "The appointment was resolved — incomplete case, no further action. The shipment was cancelled following a late review. The team reported a late issue; the ticket was resolved. The account was approved after an automatic check.", created_at: new Date("2023-06-09T20:33:22Z"), topic: "discussion innovation skills", likes: 376 },
            { id: 48, user_id: 152, content: "No response from support, so the record was delayed. The document was refunded — standard case, no further action.", created_at: new Date("2023-06-28T20:01:12Z"), topic: "skills", likes: 581 },
            { id: 49, user_id: 7, content: "A late follow-up: the ticket was rejected. The account owner confirmed the details and the payment was rescheduled. The delivery was reviewed after a late check. The courier confirmed the details and the booking was resolved.", created_at: new Date("2023-08-28T13:10:11Z"), topic: "learning", likes: 683 },
            { id: 50, user_id: 161, content: "Support reported a repeat issue; the transfer was delayed. The supplier confirmed the details and the appointment was reopened.", created_at: new Date("2023-01-26T18:32:27Z"), topic: "education development learning", likes: 782 },
            { id: 51, user_id: 120, content: "Support confirmed the details and the delivery was replaced. A repeat document was completed the same day.", created_at: new Date("2023-01-18T12:33:15Z"), topic: "engagement innovation collaboration", likes: 348 },
            { id: 52, user_id: 47, content: "The appointment was escalated — urgent case, no further action. An operator asked for a change and the account was reopened.", created_at: new Date("2023-08-04T12:20:12Z"), topic: "education collaboration skills community resources", likes: 326 },
            { id: 53, user_id: 101, content: "The account was reviewed after an incomplete check. The supplier confirmed the details and the refund was refunded. The account owner asked for a change and the refund was resolved. The order was confirmed — automatic case, no further action.", created_at: new Date("2023-01-05T07:36:20Z"), topic: "education skills", likes: 377 },
            { id: 54, user_id: 93, content: "The shipment was reopened — minor case, no further action. The courier asked for a change and the shipment was closed. The item was rescheduled after a repeat check. The claim was completed after a minor check.", created_at: new Date("2023-10-30T00:24:57Z"), topic: "networking engagement", likes: 821 },
            { id: 55, user_id: 66, content: "A repeat follow-up: the delivery was confirmed. The session was replaced following a duplicate review.", created_at: new Date("2023-01-31T21:53:12Z"), topic: "education networking feedback", likes: 462 },
            { id: 56, user_id: 140, content: "A duplicate payment was confirmed the same day. A duplicate follow-up: the session was delayed.", created_at: new Date("2023-01-18T19:02:15Z"), topic: "education resources community feedback learning", likes: 270 },
            { id: 57, user_id: 51, content: "The customer asked for a change and the invoice was delayed. Flagged as automatic. The courier updated the invoice. A standard payment was delayed the same day. No response from the supplier, so the delivery was closed.", created_at: new Date("2023-08-30T15:53:01Z"), topic: "learning networking", likes: 298 },
            { id: 58, user_id: 51, content: "The document was refunded — urgent case, no further action. The supplier asked for a change and the refund was refunded. An incomplete document was processed the same day. An operator asked for a change and the refund was rejected.", created_at: new Date("2023-07-07T07:08:32Z"), topic: "learning resources networking education discussion", likes: 441 },
            { id: 59, user_id: 100, content: "Flagged as standard. The supplier rejected the shipment. The appointment was completed following a duplicate review.", created_at: new Date("2023-07-27T17:58:21Z"), topic: "collaboration education networking engagement resources", likes: 580 },
            { id: 60, user_id: 16, content: "The document was cancelled — incomplete case, no further action. A repeat ticket was rejected the same day. The item was cancelled following a late review.", created_at: new Date("2023-05-21T09:35:10Z"), topic: "development engagement community education", likes: 364 },
            { id: 61, user_id: 43, content: "The reviewer reported a partial issue; the claim was updated. The courier asked for a change and the session was escalated.", created_at: new Date("2023-08-29T20:50:29Z"), topic: "resources innovation", likes: 487 },
            { id: 62, user_id: 32, content: "Flagged as automatic. The customer reopened the document. A duplicate follow-up: the record was refunded.", created_at: new Date("2023-01-10T19:30:52Z"), topic: "skills community", likes: 339 },
            { id: 63, user_id: 86, content: "The request was updated — duplicate case, no further action. An urgent record was processed the same day. The payment was closed after a routine check. Flagged as late. Support escalated the refund.", created_at: new Date("2023-03-18T09:22:01Z"), topic: "feedback development skills community innovation", likes: 767 },
            { id: 64, user_id: 166, content: "Flagged as manual. The reviewer confirmed the payment. The report was resolved after a standard check.", created_at: new Date("2023-06-27T19:19:06Z"), topic: "collaboration", likes: 519 },
            { id: 65, user_id: 126, content: "The record was approved — partial case, no further action. The invoice was delayed after a minor check.", created_at: new Date("2023-12-11T17:55:16Z"), topic: "collaboration", likes: 370 },
            { id: 66, user_id: 93, content: "The reviewer asked for a change and the payment was resolved. The account was processed following an incomplete review. No response from the customer, so the ticket was replaced.", created_at: new Date("2023-01-30T23:43:57Z"), topic: "collaboration networking discussion learning community", likes: 582 },
            { id: 67, user_id: 106, content: "The customer reported a routine issue; the report was replaced. Flagged as minor. The team reopened the report.", created_at: new Date("2023-11-18T12:52:15Z"), topic: "resources learning development education", likes: 542 },
            { id: 68, user_id: 77, content: "The shipment was rejected after an unusual check. A manual follow-up: the delivery was rescheduled. The team asked for a change and the item was delayed. A minor ticket was delayed the same day.", created_at: new Date("2023-11-23T15:22:33Z"), topic: "skills collaboration resources learning", likes: 352 },
            { id: 69, user_id: 165, content: "The account owner confirmed the details and the request was refunded. Support reported a late issue; the shipment was confirmed.", created_at: new Date("2023-02-05T13:19:29Z"), topic: "feedback education engagement networking", likes: 662 },
            { id: 70, user_id: 194, content: "A manual follow-up: the shipment was reviewed. The request was reviewed following a manual review. The ticket was completed after an urgent check.", created_at: new Date("2023-05-18T19:12:43Z"), topic: "education development collaboration engagement networking", likes: 343 },
            { id: 71, user_id: 126, content: "The refund was delayed after a standard check. The appointment was cancelled following an urgent review.", created_at: new Date("2023-09-24T19:08:19Z"), topic: "resources discussion feedback learning", likes: 350 },
            { id: 72, user_id: 147, content: "Flagged as late. An operator reviewed the refund. The ticket was reviewed — minor case, no further action.", created_at: new Date("2023-08-21T18:01:01Z"), topic: "feedback innovation", likes: 479 },
            { id: 73, user_id: 156, content: "Flagged as unusual. The team updated the item. An automatic session was updated the same day.", created_at: new Date("2023-08-18T15:56:52Z"), topic: "education learning", likes: 292 },
            { id: 74, user_id: 132, content: "The ticket was reviewed following a repeat review. Flagged as repeat. The courier rejected the account. The team asked for a change and the transfer was delayed. The account owner reported an urgent issue; the report was refunded.", created_at: new Date("2023-11-04T17:32:19Z"), topic: "development learning discussion networking community", likes: 758 },
            { id: 75, user_id: 2, content: "Flagged as urgent. The courier resolved the record. The account owner confirmed the details and the report was cancelled.", created_at: new Date("2023-10-05T10:22:40Z"), topic: "networking", likes: 401 },
            { id: 76, user_id: 54, content: "The claim was completed after a manual check. The account was updated after a standard check. No response from support, so the request was resolved.", created_at: new Date("2023-09-29T19:45:49Z"), topic: "skills community discussion development", likes: 187 },
            { id: 77, user_id: 10, content: "Flagged as automatic. The reviewer replaced the ticket. An unusual shipment was approved the same day.", created_at: new Date("2023-05-06T12:03:40Z"), topic: "discussion innovation community", likes: 598 },
            { id: 78, user_id: 105, content: "An operator asked for a change and the payment was reopened. The booking was resolved following a partial review.", created_at: new Date("2023-08-17T20:44:28Z"), topic: "discussion", likes: 299 },
            { id: 79, user_id: 197, content: "No response from the courier, so the session was updated. The reviewer reported an incomplete issue; the document was closed.", created_at: new Date("2023-01-20T18:42:50Z"), topic: "feedback development resources learning", likes: 474 },
            { id: 80, user_id: 108, content: "No response from the account owner, so the document was reviewed. The appointment was delayed after a routine check.", created_at: new Date("2023-12-30T19:44:48Z"), topic: "community innovation learning", likes: 237 },
            { id: 81, user_id: 67, content: "An urgent follow-up: the ticket was completed. No response from the account owner, so the order was reviewed.", created_at: new Date("2023-09-17T19:55:30Z"), topic: "collaboration", likes: 508 },
            { id: 82, user_id: 72, content: "The courier confirmed the details and the request was resolved. The refund was refunded after an incomplete check.", created_at: new Date("2023-09-09T11:15:02Z"), topic: "resources engagement feedback learning", likes: 400 },
            { id: 83, user_id: 167, content: "The report was replaced after an automatic check. The request was processed following a duplicate review. A duplicate request was updated the same day. Flagged as late. The account owner completed the ticket.", created_at: new Date("2023-08-08T05:38:07Z"), topic: "education", likes: 368 },
            { id: 84, user_id: 13, content: "Flagged as late. The supplier closed the claim. Support asked for a change and the account was rescheduled.", created_at: new Date("2023-12-23T19:01:53Z"), topic: "feedback community", likes: 408 },
            { id: 85, user_id: 100, content: "The payment was processed following a manual review. An urgent follow-up: the session was updated. No response from support, so the transfer was delayed. The shipment was updated after a manual check.", created_at: new Date("2023-03-31T18:24:21Z"), topic: "discussion collaboration engagement networking innovation", likes: 699 },
            { id: 86, user_id: 44, content: "The appointment was refunded following an incomplete review. Flagged as late. The team updated the claim.", created_at: new Date("2023-03-17T15:28:53Z"), topic: "learning feedback discussion engagement", likes: 497 },
            { id: 87, user_id: 34, content: "The transfer was completed following an automatic review. The team reported an urgent issue; the claim was refunded. The claim was updated following a partial review. The document was replaced — routine case, no further action.", created_at: new Date("2023-08-14T22:30:18Z"), topic: "skills learning feedback resources education", likes: 741 },
            { id: 88, user_id: 158, content: "A late account was cancelled the same day. No response from the customer, so the order was approved.", created_at: new Date("2023-02-16T19:21:07Z"), topic: "networking feedback innovation", likes: 414 },
            { id: 89, user_id: 116, content: "No response from the team, so the report was approved. The courier asked for a change and the invoice was replaced.", created_at: new Date("2023-03-17T20:56:58Z"), topic: "collaboration community innovation", likes: 280 },
            { id: 90, user_id: 38, content: "The reviewer confirmed the details and the session was reviewed. The claim was updated — late case, no further action.", created_at: new Date("2023-01-09T06:59:55Z"), topic: "skills innovation resources engagement", likes: 558 },
            { id: 91, user_id: 16, content: "The report was confirmed after a duplicate check. The courier reported a minor issue; the appointment was resolved. The team confirmed the details and the shipment was closed.", created_at: new Date("2023-11-21T14:33:07Z"), topic: "innovation learning development resources feedback", likes: 495 },
            { id: 92, user_id: 165, content: "The claim was completed — standard case, no further action. The reviewer reported a late issue; the report was rescheduled. An operator confirmed the details and the shipment was closed. A standard follow-up: the delivery was escalated.", created_at: new Date("2023-08-16T08:21:00Z"), topic: "innovation networking", likes: 530 },
            { id: 93, user_id: 196, content: "A standard follow-up: the transfer was processed. No response from the team, so the order was reopened. No response from an operator, so the session was cancelled.", created_at: new Date("2023-08-20T23:45:13Z"), topic: "learning collaboration innovation networking discussion", likes: 455 },
            { id: 94, user_id: 38, content: "The record was reopened following a manual review. An incomplete follow-up: the payment was rejected. A routine follow-up: the report was closed. An unusual follow-up: the invoice was replaced.", created_at: new Date("2023-03-11T19:00:08Z"), topic: "collaboration feedback engagement learning", likes: 558 },
            { id: 95, user_id: 59, content: "The account was confirmed following a routine review. An operator asked for a change and the account was reopened. The reviewer asked for a change and the report was reviewed.", created_at: new Date("2023-10-30T18:06:03Z"), topic: "innovation engagement learning resources development", likes: 395 },
            { id: 96, user_id: 147, content: "A duplicate follow-up: the delivery was reviewed. An operator reported a standard issue; the report was reviewed.", created_at: new Date("2023-10-08T03:54:06Z"), topic: "development resources education feedback learning", likes: 511 },
            { id: 97, user_id: 103, content: "The account owner confirmed the details and the item was rescheduled. No response from the account owner, so the ticket was rescheduled. Flagged as routine. The team updated the record. The document was reopened after a late check.", created_at: new Date("2023-09-23T11:25:55Z"), topic: "learning networking engagement discussion", likes: 391 },
            { id: 98, user_id: 104, content: "No response from support, so the delivery was confirmed. No response from the supplier, so the shipment was refunded. An operator reported a duplicate issue; the shipment was replaced. A late document was updated the same day.", created_at: new Date("2023-06-13T18:29:53Z"), topic: "innovation feedback engagement networking", likes: 398 },
            { id: 99, user_id: 190, content: "The reviewer confirmed the details and the document was rescheduled. The invoice was processed after a manual check. The session was rescheduled after a routine check. Flagged as manual. The reviewer refunded the order.", created_at: new Date("2023-06-16T15:31:12Z"), topic: "networking", likes: 265 },
            { id: 100, user_id: 139, content: "The transfer was resolved — duplicate case, no further action. The document was rescheduled after a partial check.", created_at: new Date("2023-11-08T18:55:09Z"), topic: "innovation skills collaboration discussion", likes: 290 },
            { id: 101, user_id: 163, content: "A standard follow-up: the delivery was processed. A standard session was reviewed the same day. The document was delayed after a standard check.", created_at: new Date("2023-07-31T12:33:50Z"), topic: "innovation community", likes: 301 },
            { id: 102, user_id: 92, content: "The payment was reopened — routine case, no further action. The reviewer reported an unusual issue; the report was resolved. The appointment was replaced following a repeat review. A late follow-up: the invoice was escalated.", created_at: new Date("2023-04-13T20:55:49Z"), topic: "collaboration community development", likes: 227 },
            { id: 103, user_id: 99, content: "An operator reported a partial issue; the session was confirmed. The payment was completed after a partial check. An operator asked for a change and the account was replaced. No response from the team, so the payment was closed.", created_at: new Date("2023-12-26T11:25:16Z"), topic: "education innovation collaboration", likes: 452 },
            { id: 104, user_id: 63, content: "A partial claim was updated the same day. An unusual delivery was processed the same day. The reviewer reported a repeat issue; the request was rejected. No response from the supplier, so the invoice was escalated.", created_at: new Date("2023-11-05T22:19:57Z"), topic: "discussion innovation community", likes: 525 },
            { id: 105, user_id: 45, content: "No response from the supplier, so the request was approved. An operator reported an incomplete issue; the request was refunded. The supplier confirmed the details and the appointment was reviewed.", created_at: new Date("2023-01-14T15:52:40Z"), topic: "networking community development skills", likes: 295 },
            { id: 106, user_id: 92, content: "No response from the supplier, so the record was approved. No response from the supplier, so the payment was delayed. An operator asked for a change and the ticket was refunded. A standard follow-up: the session was reviewed.", created_at: new Date("2023-11-07T19:05:35Z"), topic: "education community engagement collaboration", likes: 198 },
            { id: 107, user_id: 114, content: "No response from the reviewer, so the appointment was resolved. The team asked for a change and the booking was confirmed.", created_at: new Date("2023-01-17T11:42:25Z"), topic: "learning discussion innovation community feedback", likes: 456 },
            { id: 108, user_id: 77, content: "The session was rejected following a late review. Flagged as late. The team completed the ticket. The request was processed following a repeat review. The document was reviewed following a late review.", created_at: new Date("2023-05-19T03:29:53Z"), topic: "community", likes: 411 },
            { id: 109, user_id: 32, content: "Flagged as automatic. The customer replaced the request. Support confirmed the details and the item was approved.", created_at: new Date("2023-01-03T16:16:46Z"), topic: "education networking", likes: 406 },
            { id: 110, user_id: 183, content: "A manual order was refunded the same day. No response from the team, so the item was replaced.", created_at: new Date("2023-07-13T19:55:45Z"), topic: "resources skills engagement innovation", likes: 366 },
            { id: 111, user_id: 185, content: "Flagged as repeat. The team processed the report. A repeat claim was rejected the same day.", created_at: new Date("2023-04-15T17:14:36Z"), topic: "skills innovation collaboration networking", likes: 500 },
            { id: 112, user_id: 191, content: "The document was reviewed after a partial check. A partial follow-up: the report was rejected. The invoice was replaced after a duplicate check. The record was escalated — routine case, no further action.", created_at: new Date("2023-08-19T23:17:15Z"), topic: "collaboration learning networking", likes: 567 },
            { id: 113, user_id: 107, content: "A duplicate payment was reopened the same day. The customer reported an incomplete issue; the document was rescheduled. The customer reported a minor issue; the record was processed.", created_at: new Date("2023-10-09T20:28:35Z"), topic: "feedback engagement networking resources collaboration", likes: 406 },
            { id: 114, user_id: 30, content: "Flagged as repeat. The supplier rescheduled the request. No response from the account owner, so the transfer was confirmed. A manual item was updated the same day. The document was resolved after a late check.", created_at: new Date("2023-11-10T08:38:41Z"), topic: "community discussion development education resources", likes: 538 },
            { id: 115, user_id: 94, content: "The payment was resolved after a late check. An incomplete request was approved the same day.", created_at: new Date("2023-07-18T16:33:25Z"), topic: "resources feedback skills learning", likes: 555 },
            { id: 116, user_id: 145, content: "The request was updated after an urgent check. A manual appointment was closed the same day. The account owner confirmed the details and the refund was closed.", created_at: new Date("2023-05-28T11:54:30Z"), topic: "resources education community development", likes: 504 },
            { id: 117, user_id: 171, content: "The delivery was rejected — automatic case, no further action. Flagged as incomplete. Support rejected the order. Flagged as manual. An operator delayed the document.", created_at: new Date("2023-03-19T15:59:58Z"), topic: "skills discussion", likes: 504 },
            { id: 118, user_id: 13, content: "Flagged as routine. The supplier approved the session. A manual claim was reviewed the same day. No response from the reviewer, so the order was confirmed. No response from the courier, so the invoice was completed.", created_at: new Date("2023-12-07T08:11:07Z"), topic: "development networking discussion", likes: 425 },
            { id: 119, user_id: 168, content: "The reviewer reported an urgent issue; the ticket was reviewed. An unusual shipment was rescheduled the same day. Flagged as partial. The team resolved the session. The document was rescheduled — duplicate case, no further action.", created_at: new Date("2023-08-27T19:59:11Z"), topic: "skills feedback development", likes: 504 },
            { id: 120, user_id: 71, content: "An unusual follow-up: the report was processed. The team confirmed the details and the appointment was rejected.", created_at: new Date("2023-08-29T17:47:00Z"), topic: "engagement development networking", likes: 344 },
            { id: 121, user_id: 1, content: "The refund was confirmed following an automatic review. The account was rejected after an urgent check.", created_at: new Date("2023-10-12T09:10:58Z"), topic: "resources networking skills engagement", likes: 441 },
            { id: 122, user_id: 118, content: "The report was rejected after a duplicate check. The customer reported a standard issue; the transfer was processed.", created_at: new Date("2023-09-08T15:41:13Z"), topic: "education collaboration", likes: 388 },
            { id: 123, user_id: 141, content: "The document was cancelled — urgent case, no further action. No response from the team, so the booking was updated. No response from support, so the refund was cancelled.", created_at: new Date("2023-11-11T21:57:44Z"), topic: "innovation development", likes: 531 },
            { id: 124, user_id: 9, content: "An incomplete follow-up: the document was resolved. A late shipment was rejected the same day.", created_at: new Date("2023-07-27T18:48:10Z"), topic: "community discussion", likes: 742 },
            { id: 125, user_id: 116, content: "The report was replaced after a late check. Flagged as late. The courier replaced the report. No response from the customer, so the session was reopened. The item was processed after an unusual check.", created_at: new Date("2023-01-09T10:04:58Z"), topic: "skills discussion resources", likes: 600 },
            { id: 126, user_id: 179, content: "The courier confirmed the details and the report was rescheduled. No response from the courier, so the claim was processed. A manual booking was updated the same day. The delivery was processed after an unusual check.", created_at: new Date("2023-02-23T15:58:24Z"), topic: "development", likes: 716 },
            { id: 127, user_id: 191, content: "Flagged as unusual. The courier rescheduled the claim. The shipment was reopened — unusual case, no further action. The document was cancelled after an incomplete check.", created_at: new Date("2023-12-23T13:38:20Z"), topic: "networking community development feedback collaboration", likes: 554 },
            { id: 128, user_id: 135, content: "No response from the courier, so the session was resolved. The report was approved after a duplicate check. The request was resolved after a partial check. The supplier confirmed the details and the invoice was rejected.", created_at: new Date("2023-08-10T21:17:24Z"), topic: "collaboration networking feedback", likes: 526 },
            { id: 129, user_id: 66, content: "The team asked for a change and the ticket was approved. Flagged as minor. The courier completed the document. The appointment was escalated — routine case, no further action. The delivery was delayed after a late check.", created_at: new Date("2023-09-23T19:33:12Z"), topic: "innovation", likes: 608 },
            { id: 130, user_id: 196, content: "The record was delayed — routine case, no further action. Flagged as urgent. The reviewer updated the shipment.", created_at: new Date("2023-01-05T23:30:41Z"), topic: "innovation networking education learning engagement", likes: 375 },
            { id: 131, user_id: 8, content: "An automatic follow-up: the payment was reopened. Support reported a standard issue; the order was approved. A standard invoice was delayed the same day.", created_at: new Date("2023-05-12T10:29:01Z"), topic: "innovation feedback learning", likes: 576 },
            { id: 132, user_id: 58, content: "The report was reviewed after a standard check. No response from an operator, so the request was approved. The ticket was reopened after a standard check. The account owner reported a repeat issue; the report was processed.", created_at: new Date("2023-10-31T12:51:10Z"), topic: "development networking", likes: 346 },
            { id: 133, user_id: 182, content: "The delivery was processed after a minor check. An operator asked for a change and the payment was confirmed. The payment was delayed — incomplete case, no further action.", created_at: new Date("2023-06-14T13:53:37Z"), topic: "resources education networking development", likes: 777 },
            { id: 134, user_id: 28, content: "Flagged as standard. The team confirmed the session. No response from support, so the invoice was refunded. An operator asked for a change and the refund was completed.", created_at: new Date("2023-05-17T16:51:38Z"), topic: "discussion community innovation", likes: 302 },
            { id: 135, user_id: 117, content: "A minor follow-up: the order was rejected. The report was confirmed — late case, no further action. An operator confirmed the details and the shipment was rescheduled.", created_at: new Date("2023-06-25T14:15:07Z"), topic: "learning innovation networking feedback education", likes: 353 },
            { id: 136, user_id: 1, content: "A late invoice was escalated the same day. The account owner reported an urgent issue; the account was escalated. The ticket was refunded — automatic case, no further action.", created_at: new Date("2023-12-15T20:57:45Z"), topic: "learning resources development", likes: 310 },
            { id: 137, user_id: 7, content: "The document was cancelled following an unusual review. The account owner asked for a change and the order was completed. The shipment was cancelled after a routine check. No response from support, so the session was escalated.", created_at: new Date("2023-09-23T22:05:06Z"), topic: "community learning resources", likes: 236 },
            { id: 138, user_id: 11, content: "Flagged as repeat. The account owner updated the appointment. Flagged as duplicate. Support updated the refund.", created_at: new Date("2023-10-07T18:15:05Z"), topic: "skills", likes: 451 },
            { id: 139, user_id: 192, content: "A partial follow-up: the account was completed. An incomplete refund was replaced the same day. Flagged as partial. The team completed the payment.", created_at: new Date("2023-04-09T17:17:22Z"), topic: "education community", likes: 637 },
            { id: 140, user_id: 95, content: "A duplicate follow-up: the document was approved. No response from the team, so the refund was confirmed. The courier reported an unusual issue; the document was delayed.", created_at: new Date("2023-01-11T18:12:35Z"), topic: "community resources learning engagement", likes: 496 },
            { id: 141, user_id: 52, content: "The appointment was rescheduled — late case, no further action. No response from an operator, so the claim was cancelled. Support confirmed the details and the document was closed. A late shipment was refunded the same day.", created_at: new Date("2023-01-09T09:46:04Z"), topic: "skills engagement community", likes: 370 },
            { id: 142, user_id: 102, content: "The team confirmed the details and the document was delayed. The reviewer asked for a change and the order was delayed. The reviewer confirmed the details and the session was updated.", created_at: new Date("2023-05-06T17:03:32Z"), topic: "education resources discussion", likes: 657 },
            { id: 143, user_id: 79, content: "Support confirmed the details and the appointment was reopened. No response from the courier, so the report was refunded.", created_at: new Date("2023-04-13T17:59:28Z"), topic: "innovation skills feedback collaboration education", likes: 584 },
            { id: 144, user_id: 169, content: "Flagged as duplicate. The team rejected the booking. The account owner confirmed the details and the session was reviewed. Flagged as incomplete. The courier reviewed the order.", created_at: new Date("2023-02-06T12:38:32Z"), topic: "learning feedback innovation", likes: 682 },
            { id: 145, user_id: 95, content: "The transfer was refunded after an unusual check. The claim was delayed following a duplicate review.", created_at: new Date("2023-05-10T07:53:43Z"), topic: "networking resources", likes: 499 },
            { id: 146, user_id: 197, content: "An operator confirmed the details and the invoice was resolved. No response from the customer, so the booking was reopened. No response from an operator, so the item was rescheduled.", created_at: new Date("2023-12-22T18:47:02Z"), topic: "discussion skills feedback engagement innovation", likes: 216 },
            { id: 147, user_id: 78, content: "The item was refunded — routine case, no further action. The appointment was replaced after an incomplete check. The reviewer asked for a change and the delivery was processed. The ticket was cancelled — partial case, no further action.", created_at: new Date("2023-06-27T17:13:35Z"), topic: "networking", likes: 763 },
            { id: 148, user_id: 137, content: "The appointment was cancelled after a standard check. The claim was resolved following a minor review. No response from support, so the refund was processed.", created_at: new Date("2023-07-20T22:45:27Z"), topic: "resources skills", likes: 414 },
            { id: 149, user_id: 138, content: "The customer confirmed the details and the delivery was reviewed. Flagged as standard. The customer confirmed the refund.", created_at: new Date("2023-04-18T18:44:57Z"), topic: "discussion feedback", likes: 272 },
            { id: 150, user_id: 57, content: "Support confirmed the details and the order was delayed. The record was resolved — urgent case, no further action. The request was rejected after a late check. The payment was escalated after a routine check.", created_at: new Date("2023-09-24T12:45:41Z"), topic: "education feedback development", likes: 506 },
            { id: 151, user_id: 42, content: "Support confirmed the details and the order was closed. No response from the supplier, so the report was reopened. Flagged as urgent. The customer processed the invoice. The claim was approved — urgent case, no further action.", created_at: new Date("2023-04-03T10:55:29Z"), topic: "networking learning education", likes: 814 },
            { id: 152, user_id: 18, content: "An automatic booking was cancelled the same day. The reviewer confirmed the details and the request was escalated. The transfer was confirmed following a routine review.", created_at: new Date("2023-03-16T00:06:08Z"), topic: "community", likes: 606 },
            { id: 153, user_id: 185, content: "Flagged as automatic. The team confirmed the delivery. No response from an operator, so the claim was delayed. The reviewer confirmed the details and the transfer was completed.", created_at: new Date("2023-01-11T01:47:02Z"), topic: "resources", likes: 584 },
            { id: 154, user_id: 122, content: "No response from the courier, so the payment was updated. The team asked for a change and the appointment was replaced. The courier confirmed the details and the refund was rescheduled.", created_at: new Date("2023-05-16T19:26:02Z"), topic: "development", likes: 462 },
            { id: 155, user_id: 99, content: "A minor follow-up: the document was replaced. The refund was reopened — urgent case, no further action.", created_at: new Date("2023-08-29T21:14:23Z"), topic: "engagement", likes: 363 },
            { id: 156, user_id: 139, content: "The shipment was cancelled following a minor review. The session was reviewed — automatic case, no further action. The courier reported a repeat issue; the order was replaced.", created_at: new Date("2023-03-18T13:45:38Z"), topic: "education", likes: 534 },
            { id: 157, user_id: 146, content: "An unusual follow-up: the refund was cancelled. A routine refund was approved the same day.", created_at: new Date("2023-01-18T10:40:18Z"), topic: "learning education engagement feedback collaboration", likes: 598 },
            { id: 158, user_id: 104, content: "The record was updated following a standard review. The account owner reported a routine issue; the account was reviewed. The account was confirmed following a repeat review.", created_at: new Date("2023-07-01T09:19:42Z"), topic: "skills resources networking learning community", likes: 352 },
            { id: 159, user_id: 145, content: "The account owner reported a minor issue; the refund was reopened. The transfer was processed after an automatic check. A minor claim was closed the same day.", created_at: new Date("2023-04-25T19:22:49Z"), topic: "discussion community", likes: 487 },
            { id: 160, user_id: 54, content: "A duplicate document was reopened the same day. A manual follow-up: the booking was reopened. Flagged as routine. The supplier delayed the item. Support asked for a change and the transfer was rejected.", created_at: new Date("2023-06-14T04:05:05Z"), topic: "skills learning", likes: 731 },
            { id: 161, user_id: 94, content: "The order was completed after a routine check. An operator confirmed the details and the shipment was delayed. The team confirmed the details and the payment was updated.", created_at: new Date("2023-05-17T17:54:10Z"), topic: "discussion community learning", likes: 595 },
            { id: 162, user_id: 96, content: "The team reported an urgent issue; the payment was updated. The courier reported a duplicate issue; the item was updated. The delivery was cancelled after an urgent check. The order was completed following a standard review.", created_at: new Date("2023-03-01T14:02:12Z"), topic: "community engagement collaboration networking", likes: 495 },
            { id: 163, user_id: 14, content: "The customer reported a partial issue; the claim was delayed. The delivery was completed following an urgent review. Flagged as urgent. An operator reopened the appointment.", created_at: new Date("2023-04-14T18:08:40Z"), topic: "innovation", likes: 301 },
            { id: 164, user_id: 94, content: "The invoice was updated after an unusual check. A partial session was reviewed the same day. The delivery was escalated following an incomplete review.", created_at: new Date("2023-04-02T12:58:15Z"), topic: "community resources", likes: 396 },
            { id: 165, user_id: 46, content: "The claim was updated — incomplete case, no further action. An operator reported an urgent issue; the session was cancelled. The account owner confirmed the details and the account was delayed. The payment was resolved following an unusual review.", created_at: new Date("2023-10-20T13:16:53Z"), topic: "discussion education skills", likes: 522 },
            { id: 166, user_id: 24, content: "The supplier asked for a change and the session was escalated. The document was delayed after a standard check. The ticket was resolved — incomplete case, no further action. The refund was confirmed — unusual case, no further action.", created_at: new Date("2023-10-15T18:43:15Z"), topic: "development collaboration learning skills", likes: 650 },
            { id: 167, user_id: 107, content: "The ticket was rejected — automatic case, no further action. An automatic follow-up: the ticket was rescheduled.", created_at: new Date("2023-07-31T18:14:24Z"), topic: "community discussion education resources", likes: 468 },
            { id: 168, user_id: 55, content: "A late report was replaced the same day. An urgent follow-up: the delivery was escalated. The customer asked for a change and the session was approved.", created_at: new Date("2023-12-27T01:49:39Z"), topic: "collaboration learning", likes: 607 },
            { id: 169, user_id: 94, content: "The customer asked for a change and the refund was refunded. The reviewer confirmed the details and the claim was cancelled. The customer confirmed the details and the request was rescheduled. A manual follow-up: the shipment was escalated.", created_at: new Date("2023-08-03T05:30:50Z"), topic: "community", likes: 363 },
            { id: 170, user_id: 197, content: "No response from the reviewer, so the report was rescheduled. The request was cancelled — routine case, no further action. The refund was approved after a partial check.", created_at: new Date("2023-03-30T06:27:02Z"), topic: "skills", likes: 316 },
            { id: 171, user_id: 167, content: "The appointment was delayed — standard case, no further action. Flagged as duplicate. The customer confirmed the document.", created_at: new Date("2023-01-25T13:16:52Z"), topic: "skills development", likes: 586 },
            { id: 172, user_id: 81, content: "The appointment was refunded — automatic case, no further action. An incomplete follow-up: the item was resolved. The order was cancelled following a routine review.", created_at: new Date("2023-09-23T12:40:55Z"), topic: "discussion feedback", likes: 435 },
            { id: 173, user_id: 74, content: "The courier reported a late issue; the order was escalated. An automatic follow-up: the payment was confirmed. Support asked for a change and the item was resolved. A manual follow-up: the document was escalated.", created_at: new Date("2023-06-07T10:43:28Z"), topic: "education discussion collaboration", likes: 440 },
            { id: 174, user_id: 36, content: "No response from the customer, so the ticket was approved. An operator reported a repeat issue; the transfer was updated.", created_at: new Date("2023-11-30T22:55:56Z"), topic: "community engagement collaboration learning feedback", likes: 482 },
            { id: 175, user_id: 171, content: "The customer reported an urgent issue; the document was reopened. The customer confirmed the details and the order was escalated.", created_at: new Date("2023-09-30T09:47:00Z"), topic: "resources innovation networking community discussion", likes: 694 },
            { id: 176, user_id: 57, content: "No response from the customer, so the appointment was escalated. The request was closed — urgent case, no further action.", created_at: new Date("2023-07-22T13:10:36Z"), topic: "discussion community resources engagement", likes: 588 },
            { id: 177, user_id: 84, content: "The transfer was escalated — incomplete case, no further action. The supplier reported a routine issue; the record was delayed. Flagged as manual. Support reopened the ticket.", created_at: new Date("2023-01-10T21:54:28Z"), topic: "discussion skills community", likes: 499 },
            { id: 178, user_id: 72, content: "The appointment was escalated after a partial check. An unusual booking was updated the same day.", created_at: new Date("2023-09-14T00:31:04Z"), topic: "learning skills engagement feedback", likes: 691 },
            { id: 179, user_id: 1, content: "The order was updated after a routine check. The document was delayed after an automatic check. The record was processed — manual case, no further action. The ticket was replaced — urgent case, no further action.", created_at: new Date("2023-11-16T11:27:04Z"), topic: "education engagement development community", likes: 309 },
            { id: 180, user_id: 47, content: "An urgent follow-up: the appointment was rejected. No response from the reviewer, so the shipment was approved. An unusual claim was approved the same day.", created_at: new Date("2023-12-17T13:40:40Z"), topic: "development feedback", likes: 738 },
            { id: 181, user_id: 103, content: "The delivery was reopened — automatic case, no further action. The refund was approved — late case, no further action. The order was reviewed — incomplete case, no further action. Flagged as manual. The courier rescheduled the order.", created_at: new Date("2023-09-27T19:28:24Z"), topic: "learning innovation education resources community", likes: 768 },
            { id: 182, user_id: 165, content: "A duplicate follow-up: the item was completed. The appointment was updated following an automatic review. The account owner confirmed the details and the session was cancelled. Flagged as late. The customer updated the invoice.", created_at: new Date("2023-09-25T10:10:43Z"), topic: "networking discussion education engagement", likes: 364 },
            { id: 183, user_id: 82, content: "The transfer was replaced following a routine review. No response from the courier, so the booking was reviewed.", created_at: new Date("2023-02-08T20:53:19Z"), topic: "innovation", likes: 216 },
            { id: 184, user_id: 98, content: "An operator confirmed the details and the refund was rescheduled. A minor follow-up: the claim was delayed. The account owner confirmed the details and the order was cancelled. The supplier reported a routine issue; the ticket was resolved.", created_at: new Date("2023-03-30T13:53:31Z"), topic: "feedback", likes: 576 },
            { id: 185, user_id: 23, content: "No response from an operator, so the session was confirmed. A routine document was cancelled the same day. The claim was rescheduled after a standard check. The claim was updated following a manual review.", created_at: new Date("2023-10-07T12:45:59Z"), topic: "skills innovation community collaboration", likes: 642 },
            { id: 186, user_id: 138, content: "The customer confirmed the details and the item was completed. The reviewer confirmed the details and the refund was processed. The transfer was completed — urgent case, no further action. Flagged as unusual. The account owner updated the account.", created_at: new Date("2023-06-10T13:58:48Z"), topic: "networking", likes: 516 },
            { id: 187, user_id: 36, content: "The item was confirmed following an unusual review. A repeat follow-up: the session was rejected.", created_at: new Date("2023-09-24T20:06:26Z"), topic: "education learning networking engagement resources", likes: 775 },
            { id: 188, user_id: 62, content: "Support asked for a change and the report was confirmed. The account owner asked for a change and the refund was resolved.", created_at: new Date("2023-02-18T13:17:33Z"), topic: "skills development engagement", likes: 401 },
            { id: 189, user_id: 143, content: "The team reported a minor issue; the account was cancelled. The account was completed following a partial review. The request was reviewed after an unusual check. Flagged as duplicate. The reviewer delayed the invoice.", created_at: new Date("2023-03-01T20:30:21Z"), topic: "learning", likes: 581 },
            { id: 190, user_id: 101, content: "An operator confirmed the details and the session was processed. No response from the team, so the item was reviewed.", created_at: new Date("2023-11-20T15:57:06Z"), topic: "development discussion community resources", likes: 191 },
            { id: 191, user_id: 77, content: "A minor booking was updated the same day. Support confirmed the details and the claim was cancelled. A manual ticket was refunded the same day. No response from the supplier, so the appointment was replaced.", created_at: new Date("2023-07-22T14:15:01Z"), topic: "development collaboration learning discussion", likes: 637 },
            { id: 192, user_id: 120, content: "A repeat order was cancelled the same day. A manual follow-up: the payment was reviewed. The customer asked for a change and the account was resolved.", created_at: new Date("2023-08-01T00:15:55Z"), topic: "resources skills feedback discussion", likes: 424 },
            { id: 193, user_id: 113, content: "Flagged as unusual. The supplier updated the claim. The supplier confirmed the details and the order was rescheduled.", created_at: new Date("2023-10-17T17:33:31Z"), topic: "community innovation discussion learning", likes: 449 },
            { id: 194, user_id: 133, content: "The claim was processed following a partial review. Flagged as partial. Support closed the session.", created_at: new Date("2023-09-27T21:00:57Z"), topic: "innovation collaboration skills discussion education", likes: 702 },
            { id: 195, user_id: 136, content: "An incomplete follow-up: the order was escalated. The shipment was rejected — partial case, no further action. The customer reported an unusual issue; the account was reviewed.", created_at: new Date("2023-03-22T18:58:22Z"), topic: "community skills learning collaboration education", likes: 482 },
            { id: 196, user_id: 170, content: "A late document was closed the same day. Support reported a partial issue; the booking was rescheduled. A manual booking was cancelled the same day. An incomplete report was updated the same day.", created_at: new Date("2023-01-17T17:15:39Z"), topic: "skills community feedback", likes: 513 },
            { id: 197, user_id: 141, content: "Flagged as urgent. The team rescheduled the item. The claim was escalated following a late review. The shipment was rejected after a duplicate check.", created_at: new Date("2023-04-04T23:50:22Z"), topic: "innovation resources community", likes: 596 },
            { id: 198, user_id: 162, content: "No response from the customer, so the request was confirmed. The document was replaced following a minor review.", created_at: new Date("2023-07-22T10:50:11Z"), topic: "discussion networking", likes: 356 },
            { id: 199, user_id: 35, content: "The refund was completed following a duplicate review. No response from the team, so the order was closed.", created_at: new Date("2023-03-09T14:26:28Z"), topic: "resources collaboration engagement community innovation", likes: 467 },
            { id: 200, user_id: 38, content: "The account owner asked for a change and the delivery was closed. The booking was completed after a minor check. The invoice was reviewed — minor case, no further action.", created_at: new Date("2023-04-28T18:23:02Z"), topic: "resources", likes: 441 },
            { id: 201, user_id: 50, content: "The delivery was reopened after an unusual check. No response from the supplier, so the order was updated. The team reported an incomplete issue; the claim was resolved.", created_at: new Date("2023-11-29T12:02:01Z"), topic: "resources development networking innovation engagement", likes: 452 },
            { id: 202, user_id: 25, content: "The courier reported a minor issue; the refund was updated. The item was cancelled — urgent case, no further action. The reviewer asked for a change and the invoice was updated.", created_at: new Date("2023-11-13T13:07:06Z"), topic: "feedback resources learning", likes: 416 },
            { id: 203, user_id: 19, content: "The customer confirmed the details and the order was rejected. The appointment was processed following a late review. The session was rejected — standard case, no further action. A duplicate follow-up: the booking was approved.", created_at: new Date("2023-10-31T21:07:15Z"), topic: "networking", likes: 539 },
            { id: 204, user_id: 110, content: "An unusual payment was processed the same day. An automatic follow-up: the claim was escalated.", created_at: new Date("2023-09-13T22:04:52Z"), topic: "discussion resources education networking feedback", likes: 370 },
            { id: 205, user_id: 136, content: "A late document was resolved the same day. The team asked for a change and the request was escalated.", created_at: new Date("2023-11-29T21:23:11Z"), topic: "community education learning innovation discussion", likes: 401 },
            { id: 206, user_id: 186, content: "The report was reviewed following an incomplete review. A minor follow-up: the item was reviewed.", created_at: new Date("2023-08-24T06:35:34Z"), topic: "discussion collaboration", likes: 318 },
            { id: 207, user_id: 98, content: "The account owner confirmed the details and the ticket was resolved. The reviewer reported a standard issue; the shipment was closed. The account was rescheduled — late case, no further action.", created_at: new Date("2023-11-24T07:47:31Z"), topic: "innovation collaboration development skills", likes: 692 },
            { id: 208, user_id: 52, content: "An urgent invoice was completed the same day. The reviewer reported a late issue; the account was reopened. The payment was rejected following a partial review. The supplier confirmed the details and the invoice was cancelled.", created_at: new Date("2023-03-30T18:03:05Z"), topic: "learning", likes: 727 },
            { id: 209, user_id: 135, content: "No response from the customer, so the refund was reviewed. An operator confirmed the details and the delivery was completed.", created_at: new Date("2023-10-16T20:40:06Z"), topic: "learning innovation", likes: 223 },
            { id: 210, user_id: 98, content: "Flagged as standard. Support reviewed the transfer. The customer reported a minor issue; the order was updated. A manual follow-up: the booking was updated. The transfer was delayed — incomplete case, no further action.", created_at: new Date("2023-08-18T12:30:15Z"), topic: "community", likes: 543 },
            { id: 211, user_id: 147, content: "The courier reported a repeat issue; the document was reviewed. A duplicate appointment was processed the same day. A routine booking was updated the same day.", created_at: new Date("2023-08-27T16:37:55Z"), topic: "collaboration discussion learning development", likes: 664 },
            { id: 212, user_id: 142, content: "The reviewer reported a minor issue; the item was rejected. An operator confirmed the details and the order was rescheduled. Flagged as urgent. The supplier approved the ticket.", created_at: new Date("2023-11-06T08:36:17Z"), topic: "feedback networking", likes: 373 },
            { id: 213, user_id: 74, content: "Flagged as manual. The customer cancelled the appointment. Flagged as unusual. The team reviewed the transfer. The shipment was confirmed after a partial check.", created_at: new Date("2023-09-20T12:18:33Z"), topic: "discussion community resources feedback", likes: 388 },
            { id: 214, user_id: 135, content: "An urgent follow-up: the appointment was updated. A manual appointment was delayed the same day. Support confirmed the details and the request was processed.", created_at: new Date("2023-03-22T13:52:19Z"), topic: "collaboration resources", likes: 489 },
            { id: 215, user_id: 188, content: "The reviewer reported a repeat issue; the item was updated. Flagged as duplicate. Support cancelled the shipment.", created_at: new Date("2023-08-08T21:20:44Z"), topic: "feedback community resources", likes: 575 },
            { id: 216, user_id: 118, content: "Flagged as repeat. The account owner reopened the appointment. The document was confirmed following a manual review. No response from the supplier, so the record was escalated.", created_at: new Date("2023-10-06T12:19:41Z"), topic: "community innovation feedback", likes: 461 },
            { id: 217, user_id: 87, content: "Support asked for a change and the account was rescheduled. Flagged as standard. The team completed the order.", created_at: new Date("2023-02-12T16:25:50Z"), topic: "education development feedback skills", likes: 278 },
            { id: 218, user_id: 107, content: "Flagged as repeat. The courier resolved the transfer. The invoice was processed — manual case, no further action. The courier confirmed the details and the transfer was cancelled. No response from the customer, so the shipment was replaced.", created_at: new Date("2023-06-06T17:15:40Z"), topic: "learning education innovation networking skills", likes: 518 },
            { id: 219, user_id: 16, content: "No response from the reviewer, so the item was approved. A standard order was updated the same day. The order was rescheduled following a partial review.", created_at: new Date("2023-07-05T00:15:56Z"), topic: "collaboration networking engagement skills", likes: 495 },
            { id: 220, user_id: 106, content: "An incomplete appointment was reopened the same day. Flagged as automatic. The courier reviewed the invoice.", created_at: new Date("2023-01-01T20:05:17Z"), topic: "engagement learning", likes: 426 },
            { id: 221, user_id: 189, content: "The courier asked for a change and the invoice was confirmed. An operator asked for a change and the request was confirmed.", created_at: new Date("2023-01-24T11:10:06Z"), topic: "resources development", likes: 628 },
            { id: 222, user_id: 61, content: "A repeat document was updated the same day. The item was rejected — standard case, no further action. The session was resolved after a late check. The supplier reported a standard issue; the appointment was replaced.", created_at: new Date("2023-09-07T21:46:29Z"), topic: "innovation", likes: 417 },
            { id: 223, user_id: 120, content: "Flagged as standard. The customer confirmed the ticket. The team asked for a change and the session was escalated. No response from the team, so the delivery was approved. An automatic follow-up: the booking was updated.", created_at: new Date("2023-07-27T23:10:54Z"), topic: "collaboration engagement discussion networking education", likes: 396 },
            { id: 224, user_id: 100, content: "The team reported an unusual issue; the request was replaced. Support asked for a change and the claim was completed. The reviewer reported an automatic issue; the booking was delayed.", created_at: new Date("2023-08-08T06:43:44Z"), topic: "discussion learning", likes: 326 },
            { id: 225, user_id: 159, content: "The ticket was refunded following a minor review. An incomplete delivery was escalated the same day. The customer reported a standard issue; the invoice was reviewed.", created_at: new Date("2023-02-19T17:52:49Z"), topic: "development", likes: 333 },
            { id: 226, user_id: 62, content: "The supplier asked for a change and the claim was escalated. The supplier asked for a change and the refund was reviewed. Flagged as minor. An operator reviewed the appointment. The team asked for a change and the booking was updated.", created_at: new Date("2023-04-14T07:06:45Z"), topic: "engagement education discussion collaboration innovation", likes: 314 },
            { id: 227, user_id: 130, content: "Support confirmed the details and the order was confirmed. The shipment was reopened after a standard check.", created_at: new Date("2023-02-16T22:56:02Z"), topic: "collaboration engagement", likes: 780 },
            { id: 228, user_id: 56, content: "No response from the account owner, so the document was rejected. The ticket was updated following a manual review. A repeat request was updated the same day. The supplier asked for a change and the payment was delayed.", created_at: new Date("2023-08-09T09:04:07Z"), topic: "education discussion learning", likes: 441 },
            { id: 229, user_id: 11, content: "The shipment was resolved following a routine review. An unusual follow-up: the request was resolved.", created_at: new Date("2023-02-13T18:37:48Z"), topic: "collaboration resources feedback", likes: 510 },
            { id: 230, user_id: 19, content: "The account owner confirmed the details and the order was reviewed. The shipment was rejected following a late review.", created_at: new Date("2023-06-08T21:16:04Z"), topic: "community discussion resources development", likes: 119 },
            { id: 231, user_id: 91, content: "An operator reported a standard issue; the item was rescheduled. A routine report was rejected the same day. No response from the customer, so the record was completed. The reviewer confirmed the details and the refund was resolved.", created_at: new Date("2023-11-03T19:58:27Z"), topic: "collaboration development", likes: 606 },
            { id: 232, user_id: 169, content: "The invoice was replaced after a routine check. An unusual shipment was approved the same day. A minor follow-up: the record was approved. The order was cancelled following an automatic review.", created_at: new Date("2023-06-24T17:59:15Z"), topic: "resources skills", likes: 381 },
            { id: 233, user_id: 17, content: "A partial follow-up: the transfer was replaced. The account was processed following an incomplete review. The customer confirmed the details and the ticket was delayed.", created_at: new Date("2023-05-02T20:13:52Z"), topic: "development", likes: 566 },
            { id: 234, user_id: 48, content: "The transfer was closed — standard case, no further action. A late payment was approved the same day. The request was rescheduled — automatic case, no further action. The payment was updated — unusual case, no further action.", created_at: new Date("2023-01-15T10:33:25Z"), topic: "learning networking engagement community", likes: 566 },
            { id: 235, user_id: 24, content: "The team confirmed the details and the session was reopened. An automatic transfer was resolved the same day.", created_at: new Date("2023-03-29T13:59:42Z"), topic: "skills collaboration development education", likes: 479 },
            { id: 236, user_id: 141, content: "The refund was resolved after a standard check. A routine account was updated the same day. A routine refund was refunded the same day.", created_at: new Date("2023-12-17T16:30:28Z"), topic: "networking collaboration development", likes: 469 },
            { id: 237, user_id: 139, content: "No response from the supplier, so the shipment was confirmed. The record was reviewed after an incomplete check. No response from the account owner, so the item was rejected. The transfer was resolved following an urgent review.", created_at: new Date("2023-06-03T17:15:03Z"), topic: "development skills community feedback", likes: 742 },
            { id: 238, user_id: 121, content: "The payment was closed — incomplete case, no further action. A late ticket was completed the same day. Flagged as manual. The supplier approved the invoice.", created_at: new Date("2023-07-02T14:17:06Z"), topic: "resources", likes: 672 },
            { id: 239, user_id: 66, content: "The item was closed following an unusual review. The team asked for a change and the invoice was replaced.", created_at: new Date("2023-01-29T18:43:21Z"), topic: "learning resources development networking", likes: 428 },
            { id: 240, user_id: 130, content: "The report was approved following an unusual review. No response from the courier, so the document was confirmed.", created_at: new Date("2023-03-10T18:21:22Z"), topic: "engagement networking community resources", likes: 591 },
            { id: 241, user_id: 200, content: "The account owner reported an unusual issue; the claim was updated. Support reported an automatic issue; the claim was reviewed.", created_at: new Date("2023-09-14T01:58:27Z"), topic: "education", likes: 631 },
            { id: 242, user_id: 26, content: "No response from the customer, so the shipment was confirmed. The customer confirmed the details and the invoice was reviewed.", created_at: new Date("2023-01-21T18:35:00Z"), topic: "skills networking engagement", likes: 725 },
            { id: 243, user_id: 68, content: "The refund was delayed after a routine check. The account was escalated — late case, no further action. An operator asked for a change and the delivery was confirmed. An urgent item was rescheduled the same day.", created_at: new Date("2023-08-05T10:03:25Z"), topic: "education innovation discussion", likes: 562 },
            { id: 244, user_id: 60, content: "The delivery was reopened following an automatic review. A repeat follow-up: the booking was escalated. An operator reported a partial issue; the item was replaced. The supplier reported an incomplete issue; the ticket was completed.", created_at: new Date("2023-02-08T13:55:58Z"), topic: "networking", likes: 560 },
            { id: 245, user_id: 52, content: "Flagged as manual. The reviewer completed the payment. The transfer was rescheduled — automatic case, no further action. The ticket was resolved after a minor check.", created_at: new Date("2023-09-05T21:37:07Z"), topic: "skills community", likes: 669 },
            { id: 246, user_id: 3, content: "An operator reported a repeat issue; the report was cancelled. No response from the customer, so the session was delayed. The order was rejected — partial case, no further action.", created_at: new Date("2023-01-23T16:56:42Z"), topic: "feedback discussion collaboration networking learning", likes: 326 },
            { id: 247, user_id: 126, content: "The team reported a late issue; the record was delayed. The reviewer confirmed the details and the document was replaced.", created_at: new Date("2023-08-23T20:29:14Z"), topic: "resources engagement networking community development", likes: 399 },
            { id: 248, user_id: 127, content: "The courier confirmed the details and the document was reopened. The delivery was cancelled following a standard review.", created_at: new Date("2023-04-24T15:10:34Z"), topic: "engagement", likes: 300 },
            { id: 249, user_id: 33, content: "The account owner reported an automatic issue; the appointment was delayed. The record was closed after a partial check.", created_at: new Date("2023-08-25T23:44:58Z"), topic: "innovation feedback", likes: 580 },
            { id: 250, user_id: 60, content: "The customer reported a repeat issue; the appointment was delayed. Flagged as standard. The reviewer approved the shipment. The record was delayed following a minor review.", created_at: new Date("2023-01-24T19:46:28Z"), topic: "resources community innovation feedback", likes: 441 },
        ],
    });
    await prisma.participation.createMany({
        data: [
            { id: 1, user_id: 200, event_id: 33, feedback: "The claim was rescheduled — duplicate case, no further action.", attendance_duration_minutes: 130, participation_type: "active" },
            { id: 2, user_id: 18, event_id: 83, feedback: "The account owner asked for a change and the claim was closed.", attendance_duration_minutes: 141, participation_type: "active" },
            { id: 3, user_id: 64, event_id: 35, feedback: "The team confirmed the details and the shipment was reopened.", attendance_duration_minutes: 104, participation_type: "passive" },
            { id: 4, user_id: 42, event_id: 57, feedback: "The shipment was approved after an automatic check.", attendance_duration_minutes: 104, participation_type: "active" },
            { id: 5, user_id: 129, event_id: 99, feedback: "An operator asked for a change and the claim was rescheduled.", attendance_duration_minutes: 134, participation_type: "active" },
            { id: 6, user_id: 19, event_id: 95, feedback: "An urgent follow-up: the claim was processed.", attendance_duration_minutes: 56, participation_type: "passive" },
            { id: 7, user_id: 65, event_id: 91, feedback: "Flagged as urgent. Support resolved the record.", attendance_duration_minutes: 105, participation_type: "active" },
            { id: 8, user_id: 76, event_id: 12, feedback: null, attendance_duration_minutes: 94, participation_type: "active" },
            { id: 9, user_id: 187, event_id: 9, feedback: "The request was rejected — partial case, no further action.", attendance_duration_minutes: 84, participation_type: "active" },
            { id: 10, user_id: 43, event_id: 96, feedback: "An incomplete report was reviewed the same day.", attendance_duration_minutes: 106, participation_type: "active" },
            { id: 11, user_id: 35, event_id: 65, feedback: "A minor follow-up: the request was completed.", attendance_duration_minutes: 82, participation_type: "active" },
            { id: 12, user_id: 11, event_id: 33, feedback: null, attendance_duration_minutes: 116, participation_type: "active" },
            { id: 13, user_id: 93, event_id: 37, feedback: "A minor ticket was rejected the same day.", attendance_duration_minutes: 127, participation_type: "active" },
            { id: 14, user_id: 157, event_id: 64, feedback: "A manual follow-up: the document was replaced.", attendance_duration_minutes: 125, participation_type: "active" },
            { id: 15, user_id: 100, event_id: 20, feedback: "The account owner confirmed the details and the claim was cancelled.", attendance_duration_minutes: 96, participation_type: "active" },
            { id: 16, user_id: 166, event_id: 73, feedback: "A partial follow-up: the booking was resolved.", attendance_duration_minutes: 143, participation_type: "active" },
            { id: 17, user_id: 96, event_id: 38, feedback: "Support asked for a change and the refund was reopened.", attendance_duration_minutes: 99, participation_type: "active" },
            { id: 18, user_id: 192, event_id: 98, feedback: "The courier asked for a change and the request was confirmed.", attendance_duration_minutes: 90, participation_type: "active" },
            { id: 19, user_id: 193, event_id: 64, feedback: "The ticket was delayed following a partial review.", attendance_duration_minutes: 96, participation_type: "active" },
            { id: 20, user_id: 187, event_id: 2, feedback: "The record was updated after an automatic check.", attendance_duration_minutes: 103, participation_type: "active" },
            { id: 21, user_id: 112, event_id: 65, feedback: "The courier confirmed the details and the delivery was rescheduled.", attendance_duration_minutes: 86, participation_type: "active" },
            { id: 22, user_id: 31, event_id: 27, feedback: "Flagged as partial. The account owner replaced the session.", attendance_duration_minutes: 96, participation_type: "passive" },
            { id: 23, user_id: 100, event_id: 48, feedback: "A routine follow-up: the refund was resolved.", attendance_duration_minutes: 71, participation_type: "passive" },
            { id: 24, user_id: 153, event_id: 75, feedback: "The courier confirmed the details and the order was refunded.", attendance_duration_minutes: 137, participation_type: "active" },
            { id: 25, user_id: 79, event_id: 13, feedback: "The record was rejected after a late check.", attendance_duration_minutes: 79, participation_type: "passive" },
            { id: 26, user_id: 123, event_id: 21, feedback: "The session was reviewed following a minor review.", attendance_duration_minutes: 141, participation_type: "active" },
            { id: 27, user_id: 100, event_id: 67, feedback: "Flagged as urgent. The courier cancelled the order.", attendance_duration_minutes: 71, participation_type: "active" },
            { id: 28, user_id: 40, event_id: 59, feedback: "An unusual follow-up: the document was refunded.", attendance_duration_minutes: 61, participation_type: "passive" },
            { id: 29, user_id: 99, event_id: 100, feedback: "A late record was updated the same day.", attendance_duration_minutes: 96, participation_type: "active" },
            { id: 30, user_id: 10, event_id: 92, feedback: "The customer confirmed the details and the shipment was processed.", attendance_duration_minutes: 106, participation_type: "active" },
            { id: 31, user_id: 171, event_id: 76, feedback: "The document was reopened after a routine check.", attendance_duration_minutes: 102, participation_type: "active" },
            { id: 32, user_id: 79, event_id: 43, feedback: "The account was refunded — late case, no further action.", attendance_duration_minutes: 109, participation_type: "active" },
            { id: 33, user_id: 172, event_id: 62, feedback: "The order was cancelled after an incomplete check.", attendance_duration_minutes: 102, participation_type: "active" },
            { id: 34, user_id: 80, event_id: 75, feedback: "A standard payment was approved the same day.", attendance_duration_minutes: 113, participation_type: "active" },
            { id: 35, user_id: 130, event_id: 27, feedback: "A late follow-up: the report was completed.", attendance_duration_minutes: 95, participation_type: "active" },
            { id: 36, user_id: 151, event_id: 17, feedback: "Support reported a partial issue; the session was delayed.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 37, user_id: 21, event_id: 91, feedback: "No response from the team, so the booking was delayed.", attendance_duration_minutes: 105, participation_type: "active" },
            { id: 38, user_id: 9, event_id: 15, feedback: "The record was resolved after an urgent check.", attendance_duration_minutes: 104, participation_type: "active" },
            { id: 39, user_id: 103, event_id: 47, feedback: "The item was cancelled following a minor review.", attendance_duration_minutes: 58, participation_type: "passive" },
            { id: 40, user_id: 92, event_id: 19, feedback: "The team reported a late issue; the booking was confirmed.", attendance_duration_minutes: 103, participation_type: "active" },
            { id: 41, user_id: 186, event_id: 17, feedback: "No response from the courier, so the shipment was delayed.", attendance_duration_minutes: 82, participation_type: "active" },
            { id: 42, user_id: 66, event_id: 82, feedback: "Flagged as partial. The team confirmed the record.", attendance_duration_minutes: 118, participation_type: "active" },
            { id: 43, user_id: 193, event_id: 92, feedback: "No response from support, so the item was completed.", attendance_duration_minutes: 88, participation_type: "active" },
            { id: 44, user_id: 151, event_id: 51, feedback: "The account owner confirmed the details and the session was rejected.", attendance_duration_minutes: 87, participation_type: "active" },
            { id: 45, user_id: 31, event_id: 58, feedback: "No response from the account owner, so the delivery was reopened.", attendance_duration_minutes: 100, participation_type: "passive" },
            { id: 46, user_id: 140, event_id: 79, feedback: "No response from the customer, so the invoice was closed.", attendance_duration_minutes: 129, participation_type: "active" },
            { id: 47, user_id: 193, event_id: 92, feedback: "The document was refunded — manual case, no further action.", attendance_duration_minutes: 100, participation_type: "passive" },
            { id: 48, user_id: 153, event_id: 63, feedback: "The supplier confirmed the details and the payment was escalated.", attendance_duration_minutes: 88, participation_type: "passive" },
            { id: 49, user_id: 28, event_id: 41, feedback: "The account owner asked for a change and the delivery was refunded.", attendance_duration_minutes: 136, participation_type: "active" },
            { id: 50, user_id: 129, event_id: 31, feedback: "An automatic follow-up: the item was approved.", attendance_duration_minutes: 131, participation_type: "active" },
            { id: 51, user_id: 158, event_id: 70, feedback: "The account owner confirmed the details and the record was processed.", attendance_duration_minutes: 146, participation_type: "passive" },
            { id: 52, user_id: 192, event_id: 84, feedback: "The booking was confirmed — unusual case, no further action.", attendance_duration_minutes: 109, participation_type: "active" },
            { id: 53, user_id: 84, event_id: 80, feedback: "The supplier confirmed the details and the order was delayed.", attendance_duration_minutes: 102, participation_type: "passive" },
            { id: 54, user_id: 174, event_id: 28, feedback: "The document was resolved after a minor check.", attendance_duration_minutes: 97, participation_type: "active" },
            { id: 55, user_id: 77, event_id: 71, feedback: "A routine follow-up: the order was confirmed.", attendance_duration_minutes: 107, participation_type: "active" },
            { id: 56, user_id: 140, event_id: 50, feedback: null, attendance_duration_minutes: 73, participation_type: "passive" },
            { id: 57, user_id: 135, event_id: 69, feedback: "The request was escalated following an unusual review.", attendance_duration_minutes: 95, participation_type: "active" },
            { id: 58, user_id: 16, event_id: 94, feedback: "An operator reported an unusual issue; the payment was replaced.", attendance_duration_minutes: 110, participation_type: "active" },
            { id: 59, user_id: 169, event_id: 38, feedback: null, attendance_duration_minutes: 69, participation_type: "active" },
            { id: 60, user_id: 54, event_id: 2, feedback: "The team asked for a change and the item was refunded.", attendance_duration_minutes: 85, participation_type: "passive" },
            { id: 61, user_id: 81, event_id: 80, feedback: "The team reported an automatic issue; the record was reviewed.", attendance_duration_minutes: 125, participation_type: "active" },
            { id: 62, user_id: 82, event_id: 70, feedback: "An operator reported an urgent issue; the document was confirmed.", attendance_duration_minutes: 135, participation_type: "passive" },
            { id: 63, user_id: 5, event_id: 19, feedback: "The invoice was completed after a late check.", attendance_duration_minutes: 127, participation_type: "active" },
            { id: 64, user_id: 101, event_id: 41, feedback: "The ticket was closed — automatic case, no further action.", attendance_duration_minutes: 95, participation_type: "passive" },
            { id: 65, user_id: 170, event_id: 9, feedback: "Flagged as urgent. The supplier updated the appointment.", attendance_duration_minutes: 165, participation_type: "active" },
            { id: 66, user_id: 54, event_id: 70, feedback: "The account owner confirmed the details and the request was resolved.", attendance_duration_minutes: 120, participation_type: "active" },
            { id: 67, user_id: 21, event_id: 26, feedback: "The customer confirmed the details and the order was delayed.", attendance_duration_minutes: 129, participation_type: "active" },
            { id: 68, user_id: 62, event_id: 51, feedback: "The order was escalated following an incomplete review.", attendance_duration_minutes: 72, participation_type: "active" },
            { id: 69, user_id: 83, event_id: 80, feedback: "The refund was confirmed after an unusual check.", attendance_duration_minutes: 135, participation_type: "passive" },
            { id: 70, user_id: 178, event_id: 9, feedback: "Flagged as minor. Support escalated the booking.", attendance_duration_minutes: 97, participation_type: "active" },
            { id: 71, user_id: 175, event_id: 82, feedback: "A manual follow-up: the transfer was closed.", attendance_duration_minutes: 103, participation_type: "passive" },
            { id: 72, user_id: 46, event_id: 53, feedback: "Flagged as partial. The reviewer delayed the item.", attendance_duration_minutes: 100, participation_type: "active" },
            { id: 73, user_id: 142, event_id: 24, feedback: "No response from the courier, so the payment was cancelled.", attendance_duration_minutes: 100, participation_type: "active" },
            { id: 74, user_id: 111, event_id: 81, feedback: "Flagged as duplicate. The supplier resolved the record.", attendance_duration_minutes: 84, participation_type: "active" },
            { id: 75, user_id: 117, event_id: 98, feedback: null, attendance_duration_minutes: 102, participation_type: "active" },
            { id: 76, user_id: 62, event_id: 93, feedback: "A minor delivery was resolved the same day.", attendance_duration_minutes: 65, participation_type: "passive" },
            { id: 77, user_id: 106, event_id: 49, feedback: "No response from the reviewer, so the refund was rejected.", attendance_duration_minutes: 127, participation_type: "active" },
            { id: 78, user_id: 33, event_id: 77, feedback: "Support reported a routine issue; the refund was rejected.", attendance_duration_minutes: 103, participation_type: "active" },
            { id: 79, user_id: 31, event_id: 55, feedback: "The shipment was approved following a routine review.", attendance_duration_minutes: 117, participation_type: "active" },
            { id: 80, user_id: 106, event_id: 50, feedback: "An operator confirmed the details and the appointment was approved.", attendance_duration_minutes: 115, participation_type: "active" },
            { id: 81, user_id: 129, event_id: 100, feedback: "The session was escalated following a repeat review.", attendance_duration_minutes: 124, participation_type: "active" },
            { id: 82, user_id: 91, event_id: 80, feedback: "Flagged as late. The reviewer rejected the claim.", attendance_duration_minutes: 89, participation_type: "passive" },
            { id: 83, user_id: 68, event_id: 96, feedback: null, attendance_duration_minutes: 92, participation_type: "active" },
            { id: 84, user_id: 140, event_id: 94, feedback: "The courier asked for a change and the appointment was refunded.", attendance_duration_minutes: 84, participation_type: "passive" },
            { id: 85, user_id: 74, event_id: 79, feedback: "The reviewer asked for a change and the refund was rejected.", attendance_duration_minutes: 127, participation_type: "passive" },
            { id: 86, user_id: 193, event_id: 15, feedback: "Flagged as duplicate. The account owner confirmed the order.", attendance_duration_minutes: 80, participation_type: "active" },
            { id: 87, user_id: 167, event_id: 76, feedback: "The item was delayed — partial case, no further action.", attendance_duration_minutes: 121, participation_type: "active" },
            { id: 88, user_id: 112, event_id: 11, feedback: "An operator asked for a change and the delivery was closed.", attendance_duration_minutes: 91, participation_type: "active" },
            { id: 89, user_id: 108, event_id: 25, feedback: "A repeat shipment was resolved the same day.", attendance_duration_minutes: 90, participation_type: "active" },
            { id: 90, user_id: 120, event_id: 90, feedback: "The delivery was closed — routine case, no further action.", attendance_duration_minutes: 88, participation_type: "active" },
            { id: 91, user_id: 158, event_id: 14, feedback: "The account owner confirmed the details and the shipment was updated.", attendance_duration_minutes: 111, participation_type: "passive" },
            { id: 92, user_id: 147, event_id: 7, feedback: "A minor booking was reopened the same day.", attendance_duration_minutes: 92, participation_type: "passive" },
            { id: 93, user_id: 195, event_id: 25, feedback: "The team asked for a change and the request was delayed.", attendance_duration_minutes: 87, participation_type: "active" },
            { id: 94, user_id: 65, event_id: 78, feedback: "Flagged as repeat. The account owner rescheduled the ticket.", attendance_duration_minutes: 107, participation_type: "active" },
            { id: 95, user_id: 65, event_id: 90, feedback: "The team confirmed the details and the refund was closed.", attendance_duration_minutes: 90, participation_type: "active" },
            { id: 96, user_id: 124, event_id: 31, feedback: "An automatic claim was replaced the same day.", attendance_duration_minutes: 106, participation_type: "active" },
            { id: 97, user_id: 102, event_id: 26, feedback: "A repeat follow-up: the payment was resolved.", attendance_duration_minutes: 99, participation_type: "active" },
            { id: 98, user_id: 44, event_id: 87, feedback: null, attendance_duration_minutes: 122, participation_type: "active" },
            { id: 99, user_id: 68, event_id: 89, feedback: "An incomplete session was updated the same day.", attendance_duration_minutes: 145, participation_type: "active" },
            { id: 100, user_id: 154, event_id: 22, feedback: "The customer confirmed the details and the payment was approved.", attendance_duration_minutes: 129, participation_type: "passive" },
            { id: 101, user_id: 22, event_id: 54, feedback: "The reviewer reported a manual issue; the ticket was rejected.", attendance_duration_minutes: 95, participation_type: "active" },
            { id: 102, user_id: 105, event_id: 91, feedback: "The customer reported an automatic issue; the delivery was closed.", attendance_duration_minutes: 107, participation_type: "active" },
            { id: 103, user_id: 80, event_id: 62, feedback: "The supplier asked for a change and the booking was replaced.", attendance_duration_minutes: 96, participation_type: "active" },
            { id: 104, user_id: 147, event_id: 84, feedback: "A routine follow-up: the invoice was reviewed.", attendance_duration_minutes: 90, participation_type: "passive" },
            { id: 105, user_id: 200, event_id: 94, feedback: "Flagged as manual. The team approved the booking.", attendance_duration_minutes: 84, participation_type: "passive" },
            { id: 106, user_id: 142, event_id: 60, feedback: "The team asked for a change and the invoice was approved.", attendance_duration_minutes: 120, participation_type: "passive" },
            { id: 107, user_id: 16, event_id: 65, feedback: "A partial follow-up: the report was updated.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 108, user_id: 198, event_id: 25, feedback: "The record was confirmed following an incomplete review.", attendance_duration_minutes: 102, participation_type: "active" },
            { id: 109, user_id: 5, event_id: 51, feedback: "The reviewer asked for a change and the document was reopened.", attendance_duration_minutes: 77, participation_type: "active" },
            { id: 110, user_id: 34, event_id: 55, feedback: "The refund was rescheduled following a late review.", attendance_duration_minutes: 110, participation_type: "active" },
            { id: 111, user_id: 133, event_id: 20, feedback: "The shipment was replaced after a manual check.", attendance_duration_minutes: 99, participation_type: "active" },
            { id: 112, user_id: 107, event_id: 46, feedback: "An automatic follow-up: the booking was rejected.", attendance_duration_minutes: 116, participation_type: "active" },
            { id: 113, user_id: 132, event_id: 23, feedback: "A duplicate session was escalated the same day.", attendance_duration_minutes: 95, participation_type: "active" },
            { id: 114, user_id: 95, event_id: 73, feedback: "The document was replaced — duplicate case, no further action.", attendance_duration_minutes: 89, participation_type: "active" },
            { id: 115, user_id: 67, event_id: 17, feedback: "The claim was confirmed following an urgent review.", attendance_duration_minutes: 98, participation_type: "active" },
            { id: 116, user_id: 30, event_id: 34, feedback: "Flagged as repeat. The reviewer reviewed the account.", attendance_duration_minutes: 88, participation_type: "active" },
            { id: 117, user_id: 53, event_id: 62, feedback: null, attendance_duration_minutes: 86, participation_type: "active" },
            { id: 118, user_id: 96, event_id: 76, feedback: "The courier reported a repeat issue; the document was rescheduled.", attendance_duration_minutes: 117, participation_type: "active" },
            { id: 119, user_id: 95, event_id: 79, feedback: "The customer reported an urgent issue; the session was closed.", attendance_duration_minutes: 84, participation_type: "passive" },
            { id: 120, user_id: 77, event_id: 47, feedback: null, attendance_duration_minutes: 78, participation_type: "active" },
            { id: 121, user_id: 23, event_id: 66, feedback: "The session was replaced — standard case, no further action.", attendance_duration_minutes: 90, participation_type: "active" },
            { id: 122, user_id: 26, event_id: 31, feedback: "An incomplete follow-up: the delivery was refunded.", attendance_duration_minutes: 104, participation_type: "active" },
            { id: 123, user_id: 178, event_id: 40, feedback: "The transfer was updated following an automatic review.", attendance_duration_minutes: 54, participation_type: "active" },
            { id: 124, user_id: 118, event_id: 10, feedback: "No response from support, so the request was reviewed.", attendance_duration_minutes: 92, participation_type: "passive" },
            { id: 125, user_id: 57, event_id: 98, feedback: "A repeat document was completed the same day.", attendance_duration_minutes: 99, participation_type: "active" },
            { id: 126, user_id: 66, event_id: 56, feedback: null, attendance_duration_minutes: 59, participation_type: "active" },
            { id: 127, user_id: 153, event_id: 38, feedback: "Flagged as minor. The supplier reviewed the appointment.", attendance_duration_minutes: 80, participation_type: "passive" },
            { id: 128, user_id: 35, event_id: 29, feedback: "The team reported a repeat issue; the item was escalated.", attendance_duration_minutes: 124, participation_type: "active" },
            { id: 129, user_id: 49, event_id: 11, feedback: "The invoice was rejected after a repeat check.", attendance_duration_minutes: 112, participation_type: "passive" },
            { id: 130, user_id: 103, event_id: 71, feedback: "The team asked for a change and the item was replaced.", attendance_duration_minutes: 108, participation_type: "active" },
            { id: 131, user_id: 94, event_id: 100, feedback: "The booking was approved — repeat case, no further action.", attendance_duration_minutes: 127, participation_type: "active" },
            { id: 132, user_id: 6, event_id: 19, feedback: "The item was reopened after a manual check.", attendance_duration_minutes: 109, participation_type: "active" },
            { id: 133, user_id: 68, event_id: 74, feedback: "Flagged as manual. The courier reopened the claim.", attendance_duration_minutes: 113, participation_type: "passive" },
            { id: 134, user_id: 104, event_id: 1, feedback: "The transfer was reopened — standard case, no further action.", attendance_duration_minutes: 106, participation_type: "active" },
            { id: 135, user_id: 127, event_id: 98, feedback: "The invoice was replaced after a routine check.", attendance_duration_minutes: 135, participation_type: "active" },
            { id: 136, user_id: 194, event_id: 13, feedback: "Flagged as automatic. The account owner confirmed the document.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 137, user_id: 183, event_id: 98, feedback: "A manual shipment was completed the same day.", attendance_duration_minutes: 113, participation_type: "passive" },
            { id: 138, user_id: 169, event_id: 21, feedback: "The account owner confirmed the details and the invoice was reopened.", attendance_duration_minutes: 110, participation_type: "passive" },
            { id: 139, user_id: 160, event_id: 79, feedback: "A standard booking was approved the same day.", attendance_duration_minutes: 125, participation_type: "active" },
            { id: 140, user_id: 66, event_id: 42, feedback: "The claim was resolved — repeat case, no further action.", attendance_duration_minutes: 116, participation_type: "active" },
            { id: 141, user_id: 118, event_id: 36, feedback: "No response from support, so the claim was completed.", attendance_duration_minutes: 134, participation_type: "active" },
            { id: 142, user_id: 192, event_id: 56, feedback: "A repeat document was closed the same day.", attendance_duration_minutes: 137, participation_type: "active" },
            { id: 143, user_id: 91, event_id: 11, feedback: "The document was escalated after a routine check.", attendance_duration_minutes: 93, participation_type: "active" },
            { id: 144, user_id: 191, event_id: 62, feedback: "No response from the team, so the account was replaced.", attendance_duration_minutes: 93, participation_type: "active" },
            { id: 145, user_id: 51, event_id: 72, feedback: null, attendance_duration_minutes: 94, participation_type: "active" },
            { id: 146, user_id: 191, event_id: 60, feedback: "The report was reopened — partial case, no further action.", attendance_duration_minutes: 79, participation_type: "passive" },
            { id: 147, user_id: 90, event_id: 92, feedback: "The account owner reported an unusual issue; the delivery was reviewed.", attendance_duration_minutes: 90, participation_type: "passive" },
            { id: 148, user_id: 112, event_id: 67, feedback: "No response from the team, so the ticket was updated.", attendance_duration_minutes: 116, participation_type: "active" },
            { id: 149, user_id: 130, event_id: 14, feedback: "The team reported an urgent issue; the report was rejected.", attendance_duration_minutes: 79, participation_type: "active" },
            { id: 150, user_id: 134, event_id: 48, feedback: "The team asked for a change and the claim was refunded.", attendance_duration_minutes: 109, participation_type: "active" },
            { id: 151, user_id: 156, event_id: 27, feedback: null, attendance_duration_minutes: 103, participation_type: "passive" },
            { id: 152, user_id: 119, event_id: 85, feedback: null, attendance_duration_minutes: 105, participation_type: "passive" },
            { id: 153, user_id: 85, event_id: 92, feedback: "The account owner reported a duplicate issue; the refund was completed.", attendance_duration_minutes: 57, participation_type: "active" },
            { id: 154, user_id: 57, event_id: 5, feedback: null, attendance_duration_minutes: 103, participation_type: "active" },
            { id: 155, user_id: 36, event_id: 37, feedback: "Support reported an automatic issue; the shipment was processed.", attendance_duration_minutes: 52, participation_type: "active" },
            { id: 156, user_id: 157, event_id: 20, feedback: "An operator reported a partial issue; the booking was processed.", attendance_duration_minutes: 83, participation_type: "active" },
            { id: 157, user_id: 180, event_id: 3, feedback: "Support confirmed the details and the record was refunded.", attendance_duration_minutes: 124, participation_type: "passive" },
            { id: 158, user_id: 84, event_id: 65, feedback: "An automatic order was refunded the same day.", attendance_duration_minutes: 126, participation_type: "active" },
            { id: 159, user_id: 63, event_id: 74, feedback: "The courier reported a standard issue; the record was cancelled.", attendance_duration_minutes: 121, participation_type: "active" },
            { id: 160, user_id: 4, event_id: 79, feedback: "An urgent session was resolved the same day.", attendance_duration_minutes: 79, participation_type: "active" },
            { id: 161, user_id: 123, event_id: 28, feedback: "The team confirmed the details and the delivery was rejected.", attendance_duration_minutes: 83, participation_type: "passive" },
            { id: 162, user_id: 63, event_id: 63, feedback: "The item was refunded following a routine review.", attendance_duration_minutes: 133, participation_type: "active" },
            { id: 163, user_id: 52, event_id: 5, feedback: null, attendance_duration_minutes: 97, participation_type: "active" },
            { id: 164, user_id: 94, event_id: 45, feedback: "The courier asked for a change and the report was closed.", attendance_duration_minutes: 122, participation_type: "active" },
            { id: 165, user_id: 125, event_id: 95, feedback: "An operator confirmed the details and the request was replaced.", attendance_duration_minutes: 94, participation_type: "passive" },
            { id: 166, user_id: 136, event_id: 28, feedback: "The refund was reviewed following a standard review.", attendance_duration_minutes: 108, participation_type: "active" },
            { id: 167, user_id: 88, event_id: 75, feedback: "The transfer was delayed — unusual case, no further action.", attendance_duration_minutes: 146, participation_type: "active" },
            { id: 168, user_id: 71, event_id: 16, feedback: "An operator confirmed the details and the invoice was resolved.", attendance_duration_minutes: 120, participation_type: "active" },
            { id: 169, user_id: 153, event_id: 57, feedback: "A repeat follow-up: the record was refunded.", attendance_duration_minutes: 96, participation_type: "active" },
            { id: 170, user_id: 67, event_id: 54, feedback: "The customer reported a minor issue; the session was closed.", attendance_duration_minutes: 127, participation_type: "active" },
            { id: 171, user_id: 75, event_id: 5, feedback: null, attendance_duration_minutes: 108, participation_type: "active" },
            { id: 172, user_id: 30, event_id: 51, feedback: "No response from the reviewer, so the transfer was approved.", attendance_duration_minutes: 110, participation_type: "active" },
            { id: 173, user_id: 54, event_id: 24, feedback: "A manual follow-up: the claim was processed.", attendance_duration_minutes: 92, participation_type: "active" },
            { id: 174, user_id: 27, event_id: 56, feedback: null, attendance_duration_minutes: 138, participation_type: "active" },
            { id: 175, user_id: 39, event_id: 79, feedback: "An automatic follow-up: the transfer was reopened.", attendance_duration_minutes: 145, participation_type: "passive" },
            { id: 176, user_id: 101, event_id: 36, feedback: "An operator asked for a change and the invoice was resolved.", attendance_duration_minutes: 120, participation_type: "active" },
            { id: 177, user_id: 27, event_id: 27, feedback: null, attendance_duration_minutes: 141, participation_type: "active" },
            { id: 178, user_id: 135, event_id: 7, feedback: "The appointment was replaced — manual case, no further action.", attendance_duration_minutes: 72, participation_type: "active" },
            { id: 179, user_id: 73, event_id: 21, feedback: "The refund was approved — routine case, no further action.", attendance_duration_minutes: 78, participation_type: "active" },
            { id: 180, user_id: 138, event_id: 61, feedback: "The courier asked for a change and the report was confirmed.", attendance_duration_minutes: 109, participation_type: "active" },
            { id: 181, user_id: 142, event_id: 18, feedback: "The courier reported an automatic issue; the order was rescheduled.", attendance_duration_minutes: 144, participation_type: "active" },
            { id: 182, user_id: 96, event_id: 64, feedback: "The refund was closed after a duplicate check.", attendance_duration_minutes: 101, participation_type: "active" },
            { id: 183, user_id: 135, event_id: 72, feedback: "The report was updated following a manual review.", attendance_duration_minutes: 120, participation_type: "active" },
            { id: 184, user_id: 159, event_id: 52, feedback: "The request was processed following a minor review.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 185, user_id: 9, event_id: 43, feedback: null, attendance_duration_minutes: 112, participation_type: "active" },
            { id: 186, user_id: 155, event_id: 37, feedback: null, attendance_duration_minutes: 128, participation_type: "active" },
            { id: 187, user_id: 31, event_id: 82, feedback: "A duplicate follow-up: the document was closed.", attendance_duration_minutes: 116, participation_type: "active" },
            { id: 188, user_id: 74, event_id: 89, feedback: "The appointment was reviewed following an urgent review.", attendance_duration_minutes: 124, participation_type: "passive" },
            { id: 189, user_id: 97, event_id: 30, feedback: "Flagged as automatic. Support updated the account.", attendance_duration_minutes: 153, participation_type: "active" },
            { id: 190, user_id: 195, event_id: 76, feedback: "The document was refunded — minor case, no further action.", attendance_duration_minutes: 119, participation_type: "active" },
            { id: 191, user_id: 19, event_id: 81, feedback: null, attendance_duration_minutes: 129, participation_type: "active" },
            { id: 192, user_id: 139, event_id: 28, feedback: "The reviewer confirmed the details and the payment was updated.", attendance_duration_minutes: 97, participation_type: "active" },
            { id: 193, user_id: 11, event_id: 27, feedback: "Support reported an urgent issue; the appointment was closed.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 194, user_id: 49, event_id: 60, feedback: "The account was completed — urgent case, no further action.", attendance_duration_minutes: 85, participation_type: "active" },
            { id: 195, user_id: 64, event_id: 14, feedback: "The report was resolved after a repeat check.", attendance_duration_minutes: 144, participation_type: "active" },
            { id: 196, user_id: 73, event_id: 60, feedback: "The customer reported an unusual issue; the record was replaced.", attendance_duration_minutes: 128, participation_type: "active" },
            { id: 197, user_id: 117, event_id: 35, feedback: "The claim was completed after a repeat check.", attendance_duration_minutes: 126, participation_type: "active" },
            { id: 198, user_id: 103, event_id: 42, feedback: "Flagged as duplicate. The customer resolved the delivery.", attendance_duration_minutes: 145, participation_type: "passive" },
            { id: 199, user_id: 187, event_id: 59, feedback: "The ticket was resolved after an automatic check.", attendance_duration_minutes: 87, participation_type: "passive" },
            { id: 200, user_id: 138, event_id: 38, feedback: "The team asked for a change and the claim was rejected.", attendance_duration_minutes: 155, participation_type: "active" },
            { id: 201, user_id: 139, event_id: 9, feedback: "A routine follow-up: the booking was approved.", attendance_duration_minutes: 112, participation_type: "active" },
            { id: 202, user_id: 112, event_id: 100, feedback: "The customer reported a late issue; the session was resolved.", attendance_duration_minutes: 91, participation_type: "passive" },
            { id: 203, user_id: 168, event_id: 6, feedback: "Support reported a late issue; the request was cancelled.", attendance_duration_minutes: 114, participation_type: "passive" },
            { id: 204, user_id: 73, event_id: 90, feedback: "An operator confirmed the details and the request was delayed.", attendance_duration_minutes: 117, participation_type: "active" },
            { id: 205, user_id: 29, event_id: 64, feedback: null, attendance_duration_minutes: 136, participation_type: "active" },
            { id: 206, user_id: 82, event_id: 94, feedback: "The refund was resolved after a late check.", attendance_duration_minutes: 103, participation_type: "active" },
            { id: 207, user_id: 93, event_id: 39, feedback: "Flagged as late. The account owner approved the booking.", attendance_duration_minutes: 106, participation_type: "passive" },
            { id: 208, user_id: 172, event_id: 8, feedback: "The invoice was rescheduled following a late review.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 209, user_id: 97, event_id: 38, feedback: null, attendance_duration_minutes: 65, participation_type: "active" },
            { id: 210, user_id: 155, event_id: 52, feedback: "The team confirmed the details and the session was reopened.", attendance_duration_minutes: 134, participation_type: "active" },
            { id: 211, user_id: 171, event_id: 91, feedback: "No response from the courier, so the delivery was reopened.", attendance_duration_minutes: 77, participation_type: "active" },
            { id: 212, user_id: 165, event_id: 79, feedback: "The reviewer confirmed the details and the document was delayed.", attendance_duration_minutes: 106, participation_type: "passive" },
            { id: 213, user_id: 40, event_id: 4, feedback: "An operator asked for a change and the session was refunded.", attendance_duration_minutes: 86, participation_type: "active" },
            { id: 214, user_id: 97, event_id: 82, feedback: null, attendance_duration_minutes: 106, participation_type: "active" },
            { id: 215, user_id: 77, event_id: 92, feedback: null, attendance_duration_minutes: 107, participation_type: "active" },
            { id: 216, user_id: 44, event_id: 95, feedback: "A repeat ticket was rescheduled the same day.", attendance_duration_minutes: 102, participation_type: "active" },
            { id: 217, user_id: 75, event_id: 56, feedback: null, attendance_duration_minutes: 96, participation_type: "active" },
            { id: 218, user_id: 127, event_id: 22, feedback: "The order was closed following a routine review.", attendance_duration_minutes: 89, participation_type: "active" },
            { id: 219, user_id: 15, event_id: 14, feedback: "The supplier reported an automatic issue; the claim was cancelled.", attendance_duration_minutes: 121, participation_type: "active" },
            { id: 220, user_id: 139, event_id: 36, feedback: "The account owner reported an urgent issue; the booking was completed.", attendance_duration_minutes: 134, participation_type: "passive" },
            { id: 221, user_id: 75, event_id: 42, feedback: "The refund was closed following an incomplete review.", attendance_duration_minutes: 105, participation_type: "active" },
            { id: 222, user_id: 153, event_id: 94, feedback: "Flagged as partial. An operator refunded the report.", attendance_duration_minutes: 72, participation_type: "active" },
            { id: 223, user_id: 21, event_id: 20, feedback: "No response from support, so the delivery was replaced.", attendance_duration_minutes: 125, participation_type: "active" },
            { id: 224, user_id: 106, event_id: 93, feedback: "A partial follow-up: the document was reopened.", attendance_duration_minutes: 85, participation_type: "active" },
            { id: 225, user_id: 131, event_id: 37, feedback: "Support reported a duplicate issue; the transfer was confirmed.", attendance_duration_minutes: 80, participation_type: "active" },
            { id: 226, user_id: 73, event_id: 5, feedback: "An operator confirmed the details and the refund was completed.", attendance_duration_minutes: 150, participation_type: "passive" },
            { id: 227, user_id: 13, event_id: 95, feedback: "An operator confirmed the details and the item was escalated.", attendance_duration_minutes: 67, participation_type: "active" },
            { id: 228, user_id: 126, event_id: 60, feedback: "No response from support, so the ticket was escalated.", attendance_duration_minutes: 133, participation_type: "passive" },
            { id: 229, user_id: 97, event_id: 67, feedback: "Flagged as repeat. The supplier escalated the payment.", attendance_duration_minutes: 87, participation_type: "passive" },
            { id: 230, user_id: 70, event_id: 11, feedback: "The courier asked for a change and the record was refunded.", attendance_duration_minutes: 132, participation_type: "active" },
            { id: 231, user_id: 61, event_id: 94, feedback: "The account was cancelled — automatic case, no further action.", attendance_duration_minutes: 138, participation_type: "active" },
            { id: 232, user_id: 19, event_id: 53, feedback: "The delivery was approved — partial case, no further action.", attendance_duration_minutes: 114, participation_type: "active" },
            { id: 233, user_id: 61, event_id: 52, feedback: "No response from support, so the booking was reopened.", attendance_duration_minutes: 94, participation_type: "passive" },
            { id: 234, user_id: 74, event_id: 92, feedback: "The request was closed following a routine review.", attendance_duration_minutes: 94, participation_type: "passive" },
            { id: 235, user_id: 49, event_id: 6, feedback: "The item was delayed following a minor review.", attendance_duration_minutes: 70, participation_type: "active" },
            { id: 236, user_id: 151, event_id: 86, feedback: "A duplicate shipment was closed the same day.", attendance_duration_minutes: 92, participation_type: "active" },
            { id: 237, user_id: 1, event_id: 51, feedback: "The ticket was escalated after a duplicate check.", attendance_duration_minutes: 118, participation_type: "active" },
            { id: 238, user_id: 33, event_id: 15, feedback: "The request was updated — urgent case, no further action.", attendance_duration_minutes: 137, participation_type: "passive" },
            { id: 239, user_id: 105, event_id: 17, feedback: "The document was cancelled — repeat case, no further action.", attendance_duration_minutes: 92, participation_type: "active" },
            { id: 240, user_id: 129, event_id: 19, feedback: "A repeat follow-up: the item was rescheduled.", attendance_duration_minutes: 134, participation_type: "active" },
            { id: 241, user_id: 184, event_id: 2, feedback: "The reviewer reported a duplicate issue; the request was updated.", attendance_duration_minutes: 119, participation_type: "active" },
            { id: 242, user_id: 34, event_id: 26, feedback: "The reviewer confirmed the details and the document was cancelled.", attendance_duration_minutes: 74, participation_type: "active" },
            { id: 243, user_id: 148, event_id: 15, feedback: null, attendance_duration_minutes: 91, participation_type: "passive" },
            { id: 244, user_id: 152, event_id: 78, feedback: "A duplicate delivery was refunded the same day.", attendance_duration_minutes: 118, participation_type: "passive" },
            { id: 245, user_id: 7, event_id: 56, feedback: "A minor appointment was rescheduled the same day.", attendance_duration_minutes: 85, participation_type: "active" },
            { id: 246, user_id: 62, event_id: 30, feedback: "The shipment was updated — manual case, no further action.", attendance_duration_minutes: 155, participation_type: "active" },
            { id: 247, user_id: 90, event_id: 6, feedback: "The team reported a manual issue; the item was refunded.", attendance_duration_minutes: 129, participation_type: "active" },
            { id: 248, user_id: 31, event_id: 11, feedback: "The record was reopened following a repeat review.", attendance_duration_minutes: 126, participation_type: "active" },
            { id: 249, user_id: 102, event_id: 26, feedback: "The customer asked for a change and the shipment was rejected.", attendance_duration_minutes: 97, participation_type: "active" },
            { id: 250, user_id: 116, event_id: 75, feedback: "An operator confirmed the details and the request was approved.", attendance_duration_minutes: 142, participation_type: "active" },
            { id: 251, user_id: 153, event_id: 60, feedback: "An operator confirmed the details and the delivery was resolved.", attendance_duration_minutes: 116, participation_type: "passive" },
            { id: 252, user_id: 71, event_id: 22, feedback: "The account owner asked for a change and the request was delayed.", attendance_duration_minutes: 120, participation_type: "active" },
            { id: 253, user_id: 113, event_id: 40, feedback: "Flagged as repeat. The account owner rescheduled the item.", attendance_duration_minutes: 95, participation_type: "active" },
            { id: 254, user_id: 40, event_id: 40, feedback: "The customer confirmed the details and the ticket was escalated.", attendance_duration_minutes: 128, participation_type: "active" },
            { id: 255, user_id: 16, event_id: 45, feedback: "The request was rescheduled following a repeat review.", attendance_duration_minutes: 97, participation_type: "passive" },
            { id: 256, user_id: 91, event_id: 81, feedback: "An urgent follow-up: the transfer was replaced.", attendance_duration_minutes: 79, participation_type: "active" },
            { id: 257, user_id: 15, event_id: 11, feedback: "An urgent transfer was confirmed the same day.", attendance_duration_minutes: 103, participation_type: "active" },
            { id: 258, user_id: 53, event_id: 42, feedback: "The reviewer asked for a change and the shipment was escalated.", attendance_duration_minutes: 77, participation_type: "active" },
            { id: 259, user_id: 146, event_id: 57, feedback: null, attendance_duration_minutes: 73, participation_type: "active" },
            { id: 260, user_id: 129, event_id: 91, feedback: "Flagged as partial. The courier reviewed the booking.", attendance_duration_minutes: 74, participation_type: "passive" },
            { id: 261, user_id: 186, event_id: 8, feedback: "An operator asked for a change and the appointment was reopened.", attendance_duration_minutes: 96, participation_type: "active" },
            { id: 262, user_id: 80, event_id: 86, feedback: "The supplier asked for a change and the transfer was completed.", attendance_duration_minutes: 141, participation_type: "active" },
            { id: 263, user_id: 180, event_id: 45, feedback: "The delivery was closed — partial case, no further action.", attendance_duration_minutes: 84, participation_type: "passive" },
            { id: 264, user_id: 165, event_id: 49, feedback: "No response from the courier, so the order was cancelled.", attendance_duration_minutes: 78, participation_type: "active" },
            { id: 265, user_id: 89, event_id: 9, feedback: "A routine transfer was reopened the same day.", attendance_duration_minutes: 105, participation_type: "active" },
            { id: 266, user_id: 161, event_id: 9, feedback: "The payment was cancelled following a minor review.", attendance_duration_minutes: 119, participation_type: "active" },
            { id: 267, user_id: 153, event_id: 43, feedback: "The invoice was reviewed after a late check.", attendance_duration_minutes: 88, participation_type: "active" },
            { id: 268, user_id: 104, event_id: 24, feedback: "A late follow-up: the session was escalated.", attendance_duration_minutes: 99, participation_type: "passive" },
            { id: 269, user_id: 152, event_id: 97, feedback: "The courier reported an automatic issue; the account was resolved.", attendance_duration_minutes: 118, participation_type: "active" },
            { id: 270, user_id: 89, event_id: 53, feedback: "Support reported an incomplete issue; the delivery was escalated.", attendance_duration_minutes: 97, participation_type: "passive" },
            { id: 271, user_id: 90, event_id: 15, feedback: "A minor request was rescheduled the same day.", attendance_duration_minutes: 121, participation_type: "passive" },
            { id: 272, user_id: 66, event_id: 100, feedback: "Support asked for a change and the appointment was completed.", attendance_duration_minutes: 106, participation_type: "active" },
            { id: 273, user_id: 19, event_id: 23, feedback: "Flagged as unusual. The courier resolved the account.", attendance_duration_minutes: 113, participation_type: "active" },
            { id: 274, user_id: 161, event_id: 88, feedback: "Flagged as standard. Support confirmed the order.", attendance_duration_minutes: 94, participation_type: "active" },
            { id: 275, user_id: 169, event_id: 19, feedback: "The record was confirmed following a duplicate review.", attendance_duration_minutes: 117, participation_type: "passive" },
            { id: 276, user_id: 197, event_id: 7, feedback: "The account owner asked for a change and the report was delayed.", attendance_duration_minutes: 94, participation_type: "active" },
            { id: 277, user_id: 169, event_id: 70, feedback: "Support confirmed the details and the report was confirmed.", attendance_duration_minutes: 112, participation_type: "active" },
            { id: 278, user_id: 87, event_id: 95, feedback: "The item was reviewed after a standard check.", attendance_duration_minutes: 83, participation_type: "active" },
            { id: 279, user_id: 140, event_id: 46, feedback: "The reviewer asked for a change and the transfer was resolved.", attendance_duration_minutes: 150, participation_type: "active" },
            { id: 280, user_id: 138, event_id: 8, feedback: "The account owner reported an incomplete issue; the delivery was updated.", attendance_duration_minutes: 153, participation_type: "passive" },
            { id: 281, user_id: 90, event_id: 85, feedback: "A partial follow-up: the refund was escalated.", attendance_duration_minutes: 107, participation_type: "passive" },
            { id: 282, user_id: 92, event_id: 98, feedback: "An unusual follow-up: the delivery was rescheduled.", attendance_duration_minutes: 99, participation_type: "active" },
            { id: 283, user_id: 91, event_id: 77, feedback: "An automatic invoice was refunded the same day.", attendance_duration_minutes: 101, participation_type: "active" },
            { id: 284, user_id: 109, event_id: 64, feedback: "The request was closed — urgent case, no further action.", attendance_duration_minutes: 138, participation_type: "active" },
            { id: 285, user_id: 176, event_id: 53, feedback: null, attendance_duration_minutes: 95, participation_type: "active" },
            { id: 286, user_id: 39, event_id: 3, feedback: "The courier reported a repeat issue; the appointment was closed.", attendance_duration_minutes: 107, participation_type: "active" },
            { id: 287, user_id: 42, event_id: 65, feedback: "No response from support, so the order was replaced.", attendance_duration_minutes: 137, participation_type: "passive" },
            { id: 288, user_id: 110, event_id: 85, feedback: null, attendance_duration_minutes: 86, participation_type: "passive" },
            { id: 289, user_id: 153, event_id: 23, feedback: "The item was rescheduled following a routine review.", attendance_duration_minutes: 139, participation_type: "active" },
            { id: 290, user_id: 160, event_id: 45, feedback: "The delivery was completed after an incomplete check.", attendance_duration_minutes: 98, participation_type: "active" },
            { id: 291, user_id: 62, event_id: 62, feedback: "A routine refund was reopened the same day.", attendance_duration_minutes: 143, participation_type: "active" },
            { id: 292, user_id: 6, event_id: 56, feedback: null, attendance_duration_minutes: 81, participation_type: "active" },
            { id: 293, user_id: 92, event_id: 87, feedback: "The appointment was refunded after an automatic check.", attendance_duration_minutes: 102, participation_type: "active" },
            { id: 294, user_id: 74, event_id: 52, feedback: "The customer asked for a change and the appointment was processed.", attendance_duration_minutes: 83, participation_type: "active" },
            { id: 295, user_id: 34, event_id: 4, feedback: "The ticket was processed following a routine review.", attendance_duration_minutes: 130, participation_type: "active" },
            { id: 296, user_id: 156, event_id: 5, feedback: "An incomplete follow-up: the session was rejected.", attendance_duration_minutes: 133, participation_type: "active" },
            { id: 297, user_id: 136, event_id: 94, feedback: "An incomplete appointment was delayed the same day.", attendance_duration_minutes: 104, participation_type: "passive" },
            { id: 298, user_id: 41, event_id: 16, feedback: null, attendance_duration_minutes: 78, participation_type: "active" },
            { id: 299, user_id: 195, event_id: 77, feedback: "A duplicate booking was confirmed the same day.", attendance_duration_minutes: 104, participation_type: "active" },
            { id: 300, user_id: 78, event_id: 22, feedback: "The document was completed — unusual case, no further action.", attendance_duration_minutes: 89, participation_type: "active" },
        ],
    });
    await prisma.user_feedback.createMany({
        data: [
            { id: 1, user_id: 170, comments: "Flagged as minor. Support updated the delivery. The document was reviewed — automatic case, no further action.", rating: 5, improvement_rating: 4 },
            { id: 2, user_id: 106, comments: "Flagged as incomplete. The reviewer escalated the session. A standard item was resolved the same day.", rating: 5, improvement_rating: 4 },
            { id: 3, user_id: 75, comments: "The transfer was reopened following a routine review. No response from the supplier, so the shipment was approved. The reviewer reported a repeat issue; the document was escalated. The shipment was processed — repeat case, no further action.", rating: 2, improvement_rating: 3 },
            { id: 4, user_id: 81, comments: "An operator asked for a change and the order was refunded. The account owner asked for a change and the ticket was resolved. The supplier confirmed the details and the shipment was updated. The account owner reported a minor issue; the session was escalated.", rating: 5, improvement_rating: 3 },
            { id: 5, user_id: 10, comments: "The customer confirmed the details and the report was confirmed. The claim was approved — repeat case, no further action.", rating: 4, improvement_rating: 2 },
            { id: 6, user_id: 108, comments: "A minor follow-up: the refund was closed. A standard follow-up: the transfer was replaced. The request was resolved after a standard check. The appointment was approved after a late check.", rating: 1, improvement_rating: 3 },
            { id: 7, user_id: 142, comments: "A minor follow-up: the account was resolved. Support confirmed the details and the item was updated. The supplier confirmed the details and the booking was reopened. A repeat claim was updated the same day.", rating: 4, improvement_rating: 5 },
            { id: 8, user_id: 130, comments: "No response from the supplier, so the appointment was escalated. The session was delayed — standard case, no further action.", rating: 5, improvement_rating: 1 },
            { id: 9, user_id: 166, comments: "Flagged as incomplete. The reviewer escalated the report. The item was processed after a minor check. Flagged as manual. The courier reviewed the booking. The courier asked for a change and the request was rejected.", rating: 4, improvement_rating: 4 },
            { id: 10, user_id: 7, comments: "The team asked for a change and the delivery was processed. The item was replaced — automatic case, no further action.", rating: 5, improvement_rating: 4 },
            { id: 11, user_id: 65, comments: "No response from the account owner, so the record was resolved. A repeat follow-up: the record was rejected.", rating: 1, improvement_rating: 5 },
            { id: 12, user_id: 20, comments: "The customer asked for a change and the delivery was updated. The account owner asked for a change and the booking was reopened.", rating: 5, improvement_rating: 3 },
            { id: 13, user_id: 197, comments: "A manual follow-up: the invoice was completed. The document was replaced following an incomplete review. No response from an operator, so the report was replaced. The ticket was cancelled following a repeat review.", rating: 2, improvement_rating: 5 },
            { id: 14, user_id: 145, comments: "The item was processed after an urgent check. The booking was approved following a late review. No response from the reviewer, so the account was resolved.", rating: 3, improvement_rating: 5 },
            { id: 15, user_id: 30, comments: "The supplier asked for a change and the ticket was confirmed. The supplier asked for a change and the order was replaced. Flagged as repeat. The reviewer confirmed the booking. The record was replaced after a minor check.", rating: 5, improvement_rating: 4 },
            { id: 16, user_id: 120, comments: "A standard follow-up: the appointment was escalated. Flagged as urgent. The courier reopened the order.", rating: 3, improvement_rating: 4 },
            { id: 17, user_id: 141, comments: "The team confirmed the details and the ticket was reopened. The session was completed following an incomplete review. No response from the account owner, so the session was updated.", rating: 5, improvement_rating: 2 },
            { id: 18, user_id: 144, comments: "No response from support, so the report was replaced. No response from support, so the document was rescheduled. An unusual follow-up: the refund was approved. No response from the team, so the shipment was completed.", rating: 2, improvement_rating: 2 },
            { id: 19, user_id: 96, comments: "An automatic document was processed the same day. A repeat record was closed the same day. Flagged as repeat. The customer replaced the record. A manual report was confirmed the same day.", rating: 1, improvement_rating: 4 },
            { id: 20, user_id: 154, comments: "The customer asked for a change and the appointment was rejected. No response from the supplier, so the record was rejected. No response from the team, so the claim was refunded. A duplicate follow-up: the shipment was completed.", rating: 1, improvement_rating: 4 },
            { id: 21, user_id: 25, comments: "The record was confirmed — automatic case, no further action. Flagged as late. The supplier processed the session.", rating: 5, improvement_rating: 5 },
            { id: 22, user_id: 194, comments: "No response from an operator, so the transfer was delayed. The courier asked for a change and the request was resolved. The document was replaced — automatic case, no further action. The customer reported an unusual issue; the payment was resolved.", rating: 3, improvement_rating: 4 },
            { id: 23, user_id: 58, comments: "The ticket was rescheduled following a routine review. An unusual delivery was rejected the same day. No response from the team, so the order was processed. An urgent shipment was rescheduled the same day.", rating: 4, improvement_rating: 5 },
            { id: 24, user_id: 128, comments: "The account was delayed — duplicate case, no further action. The account owner confirmed the details and the shipment was closed. An urgent request was processed the same day.", rating: 5, improvement_rating: 2 },
            { id: 25, user_id: 185, comments: "No response from an operator, so the request was closed. The record was closed — repeat case, no further action. The customer asked for a change and the session was processed.", rating: 4, improvement_rating: 1 },
            { id: 26, user_id: 80, comments: "An incomplete claim was cancelled the same day. A manual follow-up: the refund was refunded. The supplier confirmed the details and the request was completed.", rating: 5, improvement_rating: 2 },
            { id: 27, user_id: 130, comments: "The item was resolved after an unusual check. A duplicate request was completed the same day.", rating: 5, improvement_rating: 5 },
            { id: 28, user_id: 56, comments: "The reviewer confirmed the details and the request was rescheduled. A partial follow-up: the item was updated.", rating: 4, improvement_rating: 5 },
            { id: 29, user_id: 151, comments: "An operator reported a late issue; the account was reviewed. An operator confirmed the details and the record was rescheduled.", rating: 3, improvement_rating: 4 },
            { id: 30, user_id: 119, comments: "A routine follow-up: the session was escalated. The supplier asked for a change and the item was cancelled. The report was closed following a manual review.", rating: 4, improvement_rating: 4 },
            { id: 31, user_id: 162, comments: "The team reported a repeat issue; the ticket was approved. A duplicate invoice was rescheduled the same day. The payment was escalated after a standard check. An operator asked for a change and the delivery was approved.", rating: 4, improvement_rating: 3 },
            { id: 32, user_id: 80, comments: "The customer reported a late issue; the session was processed. The team confirmed the details and the payment was completed.", rating: 5, improvement_rating: 3 },
            { id: 33, user_id: 25, comments: "A routine follow-up: the claim was closed. A manual follow-up: the account was reviewed. The courier reported a repeat issue; the order was refunded.", rating: 3, improvement_rating: 5 },
            { id: 34, user_id: 54, comments: "Flagged as routine. The team closed the document. The item was cancelled following a duplicate review.", rating: 4, improvement_rating: 4 },
            { id: 35, user_id: 83, comments: "The delivery was delayed following a routine review. The courier confirmed the details and the booking was resolved. The account was refunded after a minor check.", rating: 5, improvement_rating: 3 },
            { id: 36, user_id: 172, comments: "A manual refund was closed the same day. Flagged as repeat. The customer refunded the report. A standard payment was replaced the same day.", rating: 4, improvement_rating: 5 },
            { id: 37, user_id: 92, comments: "The courier confirmed the details and the session was replaced. Support confirmed the details and the claim was escalated. No response from an operator, so the ticket was refunded.", rating: 5, improvement_rating: 4 },
            { id: 38, user_id: 121, comments: "No response from the reviewer, so the report was updated. An automatic follow-up: the claim was reviewed. Flagged as manual. The reviewer updated the ticket. The supplier confirmed the details and the booking was cancelled.", rating: 2, improvement_rating: 4 },
            { id: 39, user_id: 117, comments: "The courier confirmed the details and the document was reopened. Support asked for a change and the payment was escalated.", rating: 5, improvement_rating: 5 },
            { id: 40, user_id: 13, comments: "The order was replaced following an urgent review. The invoice was delayed — partial case, no further action.", rating: 5, improvement_rating: 3 },
            { id: 41, user_id: 1, comments: "The report was resolved after a late check. A duplicate follow-up: the record was closed.", rating: 2, improvement_rating: 5 },
            { id: 42, user_id: 193, comments: "Flagged as incomplete. An operator completed the invoice. The session was updated — late case, no further action.", rating: 4, improvement_rating: 3 },
            { id: 43, user_id: 172, comments: "The reviewer reported a minor issue; the transfer was replaced. The session was updated after a partial check.", rating: 4, improvement_rating: 5 },
            { id: 44, user_id: 60, comments: "A minor invoice was cancelled the same day. Flagged as routine. The courier escalated the ticket. The courier asked for a change and the item was delayed. The courier confirmed the details and the booking was rejected.", rating: 5, improvement_rating: 5 },
            { id: 45, user_id: 187, comments: "Flagged as partial. The account owner approved the session. Flagged as routine. The reviewer updated the account.", rating: 5, improvement_rating: 5 },
            { id: 46, user_id: 7, comments: "The courier reported a minor issue; the order was delayed. Support reported an automatic issue; the booking was updated. A duplicate transfer was delayed the same day.", rating: 3, improvement_rating: 4 },
            { id: 47, user_id: 24, comments: "The request was approved — routine case, no further action. The reviewer reported a repeat issue; the account was closed. A manual claim was processed the same day. Flagged as minor. The reviewer processed the report.", rating: 4, improvement_rating: 4 },
            { id: 48, user_id: 34, comments: "An operator reported a partial issue; the shipment was closed. Flagged as minor. The customer confirmed the account. Flagged as incomplete. The team completed the shipment.", rating: 5, improvement_rating: 2 },
            { id: 49, user_id: 176, comments: "A standard document was escalated the same day. The team confirmed the details and the session was updated. An operator asked for a change and the shipment was cancelled.", rating: 5, improvement_rating: 5 },
            { id: 50, user_id: 104, comments: "The session was rescheduled after a late check. No response from the customer, so the delivery was replaced. The item was approved — partial case, no further action.", rating: 3, improvement_rating: 2 },
            { id: 51, user_id: 71, comments: "A repeat follow-up: the appointment was refunded. The payment was delayed after a duplicate check. Flagged as urgent. Support confirmed the ticket. The reviewer asked for a change and the shipment was confirmed.", rating: 4, improvement_rating: 4 },
            { id: 52, user_id: 10, comments: "No response from the reviewer, so the session was confirmed. The reviewer confirmed the details and the document was processed.", rating: 4, improvement_rating: 5 },
            { id: 53, user_id: 72, comments: "The refund was completed after an automatic check. No response from the team, so the booking was confirmed. The customer asked for a change and the session was processed.", rating: 5, improvement_rating: 5 },
            { id: 54, user_id: 142, comments: "The order was escalated — partial case, no further action. The report was processed following a duplicate review.", rating: 5, improvement_rating: 3 },
            { id: 55, user_id: 34, comments: "An automatic follow-up: the session was rejected. An unusual follow-up: the payment was cancelled. No response from support, so the session was reviewed. The ticket was refunded after an urgent check.", rating: 2, improvement_rating: 5 },
            { id: 56, user_id: 110, comments: "An unusual follow-up: the report was closed. A manual item was delayed the same day. A manual booking was reviewed the same day. A standard follow-up: the order was reviewed.", rating: 4, improvement_rating: 5 },
            { id: 57, user_id: 102, comments: "The record was updated — repeat case, no further action. The appointment was replaced following a late review.", rating: 5, improvement_rating: 3 },
            { id: 58, user_id: 153, comments: "The payment was delayed following a routine review. A minor item was processed the same day.", rating: 4, improvement_rating: 5 },
            { id: 59, user_id: 139, comments: "The delivery was escalated after a duplicate check. A minor follow-up: the payment was replaced.", rating: 5, improvement_rating: 4 },
            { id: 60, user_id: 139, comments: "The reviewer confirmed the details and the session was completed. Support confirmed the details and the session was escalated. An operator asked for a change and the invoice was refunded. A manual claim was rescheduled the same day.", rating: 2, improvement_rating: 1 },
            { id: 61, user_id: 52, comments: "No response from the customer, so the order was replaced. The team reported a partial issue; the appointment was refunded.", rating: 2, improvement_rating: 3 },
            { id: 62, user_id: 29, comments: "The item was delayed — partial case, no further action. The supplier reported a late issue; the appointment was escalated. A standard follow-up: the appointment was cancelled.", rating: 3, improvement_rating: 4 },
            { id: 63, user_id: 187, comments: "The reviewer confirmed the details and the record was delayed. The account was reopened — urgent case, no further action. No response from the reviewer, so the transfer was completed. Flagged as repeat. The team replaced the record.", rating: 4, improvement_rating: 1 },
            { id: 64, user_id: 186, comments: "A minor follow-up: the transfer was rescheduled. An incomplete document was reviewed the same day. A manual follow-up: the shipment was confirmed. A partial follow-up: the delivery was rescheduled.", rating: 4, improvement_rating: 2 },
            { id: 65, user_id: 112, comments: "No response from support, so the item was delayed. The shipment was rejected after a standard check. An operator confirmed the details and the transfer was rescheduled.", rating: 5, improvement_rating: 5 },
            { id: 66, user_id: 185, comments: "The booking was replaced following a standard review. The session was reopened following a routine review. An incomplete follow-up: the record was replaced.", rating: 5, improvement_rating: 5 },
            { id: 67, user_id: 12, comments: "No response from the account owner, so the invoice was cancelled. The account was rejected after a standard check. A standard session was completed the same day. An incomplete follow-up: the refund was confirmed.", rating: 5, improvement_rating: 2 },
            { id: 68, user_id: 33, comments: "No response from support, so the order was completed. The shipment was escalated following a standard review. An operator confirmed the details and the shipment was closed.", rating: 5, improvement_rating: 5 },
            { id: 69, user_id: 99, comments: "The supplier confirmed the details and the report was processed. An automatic follow-up: the session was reviewed. A manual payment was reopened the same day.", rating: 1, improvement_rating: 5 },
            { id: 70, user_id: 139, comments: "The reviewer reported a duplicate issue; the shipment was delayed. No response from an operator, so the record was refunded. The report was reviewed following a repeat review.", rating: 1, improvement_rating: 5 },
            { id: 71, user_id: 52, comments: "An unusual account was closed the same day. The team confirmed the details and the shipment was escalated. The shipment was confirmed — automatic case, no further action. No response from the account owner, so the booking was reviewed.", rating: 5, improvement_rating: 3 },
            { id: 72, user_id: 149, comments: "The customer reported an automatic issue; the booking was reopened. Support confirmed the details and the report was resolved.", rating: 5, improvement_rating: 3 },
            { id: 73, user_id: 28, comments: "Support asked for a change and the transfer was reviewed. The report was updated following a repeat review. The customer asked for a change and the document was cancelled. No response from the reviewer, so the session was refunded.", rating: 5, improvement_rating: 3 },
            { id: 74, user_id: 30, comments: "The customer asked for a change and the account was completed. Flagged as standard. The reviewer rescheduled the item.", rating: 2, improvement_rating: 3 },
            { id: 75, user_id: 200, comments: "The claim was cancelled after an unusual check. Flagged as standard. The supplier processed the shipment. The payment was escalated — duplicate case, no further action.", rating: 2, improvement_rating: 5 },
            { id: 76, user_id: 18, comments: "A repeat invoice was approved the same day. The report was completed following an automatic review. Support confirmed the details and the account was rejected. An unusual invoice was resolved the same day.", rating: 5, improvement_rating: 2 },
            { id: 77, user_id: 42, comments: "No response from support, so the appointment was replaced. The payment was approved — unusual case, no further action.", rating: 5, improvement_rating: 5 },
            { id: 78, user_id: 56, comments: "The supplier asked for a change and the claim was closed. An incomplete follow-up: the document was delayed.", rating: 5, improvement_rating: 4 },
            { id: 79, user_id: 102, comments: "Flagged as minor. The supplier rescheduled the invoice. An operator asked for a change and the invoice was reopened. Flagged as repeat. The customer reviewed the item. The document was reopened after a manual check.", rating: 2, improvement_rating: 5 },
            { id: 80, user_id: 3, comments: "No response from support, so the refund was reopened. The account owner reported a minor issue; the transfer was delayed. Support reported an automatic issue; the session was confirmed. The claim was escalated following a standard review.", rating: 5, improvement_rating: 3 },
            { id: 81, user_id: 176, comments: "Support confirmed the details and the transfer was delayed. The supplier asked for a change and the appointment was rescheduled. Flagged as urgent. The customer refunded the request.", rating: 5, improvement_rating: 5 },
            { id: 82, user_id: 24, comments: "The document was updated after a manual check. Flagged as routine. The supplier updated the order. The item was confirmed — incomplete case, no further action.", rating: 5, improvement_rating: 3 },
            { id: 83, user_id: 146, comments: "The appointment was processed — partial case, no further action. A standard follow-up: the session was processed.", rating: 2, improvement_rating: 2 },
            { id: 84, user_id: 195, comments: "No response from the customer, so the claim was reopened. Flagged as routine. The account owner refunded the appointment. The request was resolved following a minor review. The booking was reviewed — urgent case, no further action.", rating: 4, improvement_rating: 5 },
            { id: 85, user_id: 147, comments: "Flagged as duplicate. The reviewer reviewed the request. The shipment was rejected — minor case, no further action. A minor follow-up: the report was refunded.", rating: 5, improvement_rating: 4 },
            { id: 86, user_id: 27, comments: "The customer confirmed the details and the invoice was escalated. The booking was rejected — standard case, no further action. The team reported a repeat issue; the ticket was closed.", rating: 5, improvement_rating: 4 },
            { id: 87, user_id: 181, comments: "No response from an operator, so the record was approved. An incomplete follow-up: the account was rescheduled.", rating: 5, improvement_rating: 4 },
            { id: 88, user_id: 2, comments: "The courier reported a duplicate issue; the booking was reopened. The ticket was approved — minor case, no further action. The reviewer asked for a change and the account was approved. The refund was processed after an unusual check.", rating: 5, improvement_rating: 1 },
            { id: 89, user_id: 163, comments: "The account was rejected — automatic case, no further action. A repeat follow-up: the claim was closed.", rating: 5, improvement_rating: 5 },
            { id: 90, user_id: 98, comments: "No response from support, so the record was rescheduled. An automatic follow-up: the request was completed. No response from the customer, so the item was replaced. A late follow-up: the refund was updated.", rating: 5, improvement_rating: 3 },
            { id: 91, user_id: 108, comments: "Flagged as routine. An operator refunded the order. No response from an operator, so the delivery was completed.", rating: 2, improvement_rating: 1 },
            { id: 92, user_id: 185, comments: "Flagged as unusual. The team rejected the document. Flagged as repeat. The customer updated the appointment.", rating: 5, improvement_rating: 5 },
            { id: 93, user_id: 68, comments: "The item was reopened — unusual case, no further action. The reviewer reported an urgent issue; the transfer was replaced. The shipment was replaced following an unusual review.", rating: 5, improvement_rating: 5 },
            { id: 94, user_id: 31, comments: "The supplier confirmed the details and the invoice was confirmed. An urgent session was processed the same day.", rating: 4, improvement_rating: 4 },
            { id: 95, user_id: 180, comments: "The record was reopened — repeat case, no further action. The team asked for a change and the order was refunded.", rating: 3, improvement_rating: 3 },
            { id: 96, user_id: 24, comments: "The account owner asked for a change and the invoice was confirmed. The courier asked for a change and the document was closed. The team asked for a change and the transfer was rejected.", rating: 3, improvement_rating: 2 },
            { id: 97, user_id: 22, comments: "A late follow-up: the account was updated. An operator reported a minor issue; the appointment was refunded.", rating: 5, improvement_rating: 5 },
            { id: 98, user_id: 121, comments: "An urgent follow-up: the item was refunded. A standard session was delayed the same day. The courier asked for a change and the ticket was delayed. No response from the customer, so the document was escalated.", rating: 3, improvement_rating: 5 },
            { id: 99, user_id: 108, comments: "A standard follow-up: the transfer was rescheduled. A manual follow-up: the claim was updated. The item was completed after a late check.", rating: 3, improvement_rating: 2 },
            { id: 100, user_id: 27, comments: "The refund was processed — routine case, no further action. The team confirmed the details and the ticket was approved. The account owner confirmed the details and the report was approved. The reviewer confirmed the details and the transfer was delayed.", rating: 5, improvement_rating: 3 },
            { id: 101, user_id: 128, comments: "The account owner reported a manual issue; the invoice was cancelled. The team reported an urgent issue; the session was closed. A partial follow-up: the transfer was processed. The document was refunded — manual case, no further action.", rating: 5, improvement_rating: 4 },
            { id: 102, user_id: 57, comments: "Flagged as unusual. The courier confirmed the session. Flagged as manual. The courier rescheduled the delivery. The claim was rejected — incomplete case, no further action. The invoice was confirmed — late case, no further action.", rating: 4, improvement_rating: 2 },
            { id: 103, user_id: 134, comments: "No response from support, so the booking was rescheduled. The session was refunded after a manual check. The report was delayed after a repeat check. The supplier confirmed the details and the invoice was escalated.", rating: 4, improvement_rating: 5 },
            { id: 104, user_id: 187, comments: "The customer reported an unusual issue; the claim was escalated. No response from the supplier, so the account was reviewed. The refund was replaced following an urgent review.", rating: 5, improvement_rating: 2 },
            { id: 105, user_id: 108, comments: "An incomplete report was rescheduled the same day. The record was updated — standard case, no further action. A minor follow-up: the document was escalated.", rating: 4, improvement_rating: 4 },
            { id: 106, user_id: 7, comments: "The transfer was delayed — standard case, no further action. The account owner asked for a change and the delivery was delayed. Flagged as routine. The reviewer rejected the appointment.", rating: 4, improvement_rating: 1 },
            { id: 107, user_id: 191, comments: "The session was resolved after a manual check. The request was escalated — automatic case, no further action. An unusual refund was rejected the same day. The supplier reported a minor issue; the delivery was approved.", rating: 2, improvement_rating: 4 },
            { id: 108, user_id: 126, comments: "An unusual follow-up: the request was rejected. The supplier asked for a change and the request was closed. The invoice was rescheduled after an automatic check. Flagged as minor. The team refunded the delivery.", rating: 2, improvement_rating: 5 },
            { id: 109, user_id: 62, comments: "Support confirmed the details and the record was cancelled. The claim was resolved following an incomplete review. The document was refunded following an unusual review.", rating: 4, improvement_rating: 4 },
            { id: 110, user_id: 173, comments: "The supplier asked for a change and the payment was replaced. The record was approved — automatic case, no further action. The invoice was updated — automatic case, no further action.", rating: 3, improvement_rating: 5 },
            { id: 111, user_id: 200, comments: "Support reported an urgent issue; the delivery was cancelled. The team reported an incomplete issue; the appointment was cancelled. The request was refunded after an incomplete check.", rating: 3, improvement_rating: 5 },
            { id: 112, user_id: 20, comments: "A minor transfer was reopened the same day. The team asked for a change and the record was rejected. The booking was confirmed after an automatic check. The claim was delayed after a duplicate check.", rating: 5, improvement_rating: 2 },
            { id: 113, user_id: 122, comments: "No response from the team, so the record was refunded. The appointment was replaced after an unusual check. The report was cancelled — routine case, no further action. The invoice was reopened following a minor review.", rating: 5, improvement_rating: 5 },
            { id: 114, user_id: 78, comments: "The account owner confirmed the details and the document was escalated. No response from an operator, so the account was rescheduled. A minor follow-up: the order was reopened.", rating: 1, improvement_rating: 4 },
            { id: 115, user_id: 110, comments: "A repeat follow-up: the account was processed. A repeat report was rescheduled the same day. The team asked for a change and the order was escalated.", rating: 4, improvement_rating: 2 },
            { id: 116, user_id: 167, comments: "The booking was escalated following an unusual review. The item was refunded after a partial check.", rating: 2, improvement_rating: 5 },
            { id: 117, user_id: 70, comments: "An incomplete order was approved the same day. The payment was closed following an incomplete review. The team reported an urgent issue; the session was reopened.", rating: 2, improvement_rating: 4 },
            { id: 118, user_id: 11, comments: "An unusual session was escalated the same day. The request was replaced after an unusual check.", rating: 5, improvement_rating: 2 },
            { id: 119, user_id: 61, comments: "Flagged as partial. The supplier closed the booking. An incomplete delivery was closed the same day.", rating: 2, improvement_rating: 4 },
            { id: 120, user_id: 173, comments: "The team asked for a change and the transfer was rejected. Support confirmed the details and the account was rejected. The customer asked for a change and the shipment was refunded.", rating: 2, improvement_rating: 5 },
            { id: 121, user_id: 89, comments: "No response from support, so the appointment was escalated. No response from the account owner, so the request was rescheduled.", rating: 5, improvement_rating: 5 },
            { id: 122, user_id: 51, comments: "The account owner reported an urgent issue; the refund was reopened. The order was processed — routine case, no further action.", rating: 2, improvement_rating: 5 },
            { id: 123, user_id: 105, comments: "The courier confirmed the details and the session was reopened. The account was escalated after a minor check.", rating: 2, improvement_rating: 3 },
            { id: 124, user_id: 73, comments: "The refund was approved — late case, no further action. An operator confirmed the details and the appointment was confirmed. The account owner asked for a change and the account was escalated. Flagged as urgent. The account owner rejected the invoice.", rating: 2, improvement_rating: 5 },
            { id: 125, user_id: 187, comments: "Flagged as unusual. The account owner confirmed the appointment. The team asked for a change and the order was refunded. An urgent account was approved the same day. The item was reopened following a standard review.", rating: 5, improvement_rating: 5 },
            { id: 126, user_id: 200, comments: "No response from an operator, so the booking was resolved. The ticket was updated — automatic case, no further action. No response from the courier, so the claim was confirmed. An urgent follow-up: the ticket was processed.", rating: 2, improvement_rating: 5 },
            { id: 127, user_id: 164, comments: "No response from the team, so the ticket was delayed. The supplier asked for a change and the invoice was completed. No response from the supplier, so the claim was completed.", rating: 5, improvement_rating: 5 },
            { id: 128, user_id: 77, comments: "The booking was delayed — urgent case, no further action. The account owner confirmed the details and the refund was escalated. Flagged as standard. The courier rescheduled the record.", rating: 5, improvement_rating: 1 },
            { id: 129, user_id: 142, comments: "An incomplete refund was closed the same day. The request was delayed after an incomplete check. A manual follow-up: the claim was rejected. The customer confirmed the details and the payment was rejected.", rating: 5, improvement_rating: 2 },
            { id: 130, user_id: 46, comments: "A manual follow-up: the shipment was updated. The team reported a manual issue; the claim was resolved. The appointment was rescheduled — manual case, no further action. The shipment was rescheduled after a standard check.", rating: 2, improvement_rating: 2 },
            { id: 131, user_id: 89, comments: "The request was rejected — incomplete case, no further action. The appointment was rescheduled — minor case, no further action. A manual follow-up: the booking was reopened.", rating: 3, improvement_rating: 4 },
            { id: 132, user_id: 200, comments: "The payment was reopened following an incomplete review. An operator reported a manual issue; the shipment was rejected.", rating: 2, improvement_rating: 4 },
            { id: 133, user_id: 14, comments: "No response from the team, so the transfer was confirmed. An operator asked for a change and the booking was approved. The appointment was rejected following a partial review.", rating: 2, improvement_rating: 4 },
            { id: 134, user_id: 100, comments: "The account owner asked for a change and the invoice was refunded. The reviewer confirmed the details and the refund was reopened. Flagged as late. The courier escalated the record. The reviewer confirmed the details and the ticket was updated.", rating: 2, improvement_rating: 1 },
            { id: 135, user_id: 42, comments: "The record was closed after an unusual check. No response from the supplier, so the document was reviewed. The booking was replaced after a manual check. A manual delivery was reviewed the same day.", rating: 2, improvement_rating: 5 },
            { id: 136, user_id: 77, comments: "No response from an operator, so the delivery was closed. A duplicate follow-up: the booking was approved.", rating: 1, improvement_rating: 2 },
            { id: 137, user_id: 79, comments: "An urgent follow-up: the ticket was rescheduled. A routine account was reopened the same day. The appointment was reopened — late case, no further action. An operator asked for a change and the session was approved.", rating: 5, improvement_rating: 3 },
            { id: 138, user_id: 91, comments: "A partial shipment was updated the same day. The document was rescheduled following a repeat review. The order was closed after an incomplete check.", rating: 5, improvement_rating: 5 },
            { id: 139, user_id: 129, comments: "The invoice was replaced after a routine check. An automatic follow-up: the payment was processed.", rating: 2, improvement_rating: 4 },
            { id: 140, user_id: 163, comments: "The appointment was rejected — standard case, no further action. The refund was refunded — duplicate case, no further action. The invoice was closed after a duplicate check.", rating: 5, improvement_rating: 4 },
            { id: 141, user_id: 31, comments: "No response from the reviewer, so the ticket was replaced. The booking was refunded — incomplete case, no further action. An automatic follow-up: the session was reopened.", rating: 3, improvement_rating: 2 },
            { id: 142, user_id: 148, comments: "The account was closed following an incomplete review. No response from the customer, so the ticket was confirmed. A duplicate transfer was replaced the same day. No response from the team, so the document was processed.", rating: 5, improvement_rating: 5 },
            { id: 143, user_id: 176, comments: "Flagged as routine. The courier delayed the transfer. Flagged as minor. The courier delayed the order. The session was rejected following a manual review. The supplier reported an unusual issue; the item was updated.", rating: 4, improvement_rating: 4 },
            { id: 144, user_id: 46, comments: "The team confirmed the details and the invoice was escalated. An incomplete account was completed the same day. A partial follow-up: the request was approved. The delivery was rejected after an urgent check.", rating: 1, improvement_rating: 2 },
            { id: 145, user_id: 44, comments: "The invoice was processed following a duplicate review. Flagged as late. The supplier reopened the item.", rating: 3, improvement_rating: 2 },
            { id: 146, user_id: 119, comments: "A minor follow-up: the refund was replaced. The customer reported a partial issue; the appointment was confirmed.", rating: 2, improvement_rating: 1 },
            { id: 147, user_id: 148, comments: "The shipment was delayed after a repeat check. No response from the customer, so the ticket was updated. No response from the reviewer, so the account was delayed. The team asked for a change and the item was cancelled.", rating: 4, improvement_rating: 4 },
            { id: 148, user_id: 7, comments: "The booking was processed following an urgent review. An urgent refund was processed the same day. The courier reported a standard issue; the account was updated. The account owner confirmed the details and the transfer was rescheduled.", rating: 2, improvement_rating: 4 },
            { id: 149, user_id: 105, comments: "Flagged as unusual. An operator completed the booking. No response from the team, so the item was confirmed. An unusual follow-up: the transfer was confirmed. An operator asked for a change and the delivery was processed.", rating: 5, improvement_rating: 3 },
            { id: 150, user_id: 110, comments: "The request was refunded after an incomplete check. The supplier reported a routine issue; the ticket was approved.", rating: 4, improvement_rating: 2 },
        ],
    });
}

main()
    .then(() => prisma.$disconnect())
    .catch(async error => {
        console.error(error);
        await prisma.$disconnect();
        process.exit(1);
    });