mirror of
https://github.com/FlowiseAI/Flowise.git
synced 2026-10-12 10:09:53 +00:00
* feat: implement scheduling functionality for AgentflowV2 - Added ScheduleQueue class for managing scheduled jobs using BullMQ. - Introduced scheduleService for creating, updating, and disabling schedules. - Integrated schedule validation and cron expression handling. - Enhanced chatflow service to manage schedules for agentflows. - Added UI components for time and day selection (TimePicker, WeekDaysPicker, MonthDaysPicker). - Updated NodeInputHandler to support new input types for scheduling. - Improved validation for schedule configurations in agentflows. * feat: implement schedule management for agentflows - Refactor ScheduleQueue to utilize executeScheduleJob for job execution. - Add new endpoints for schedule status retrieval and enabling/disabling schedules in chatflows. - Update chatflow service to handle schedule creation, updates, and deletions more effectively. - Introduce DatePicker component for date input in UI. - Enhance CanvasHeader to manage schedule state and toggle functionality. - Integrate schedule validation logic to ensure proper configuration before enabling schedules. - Update dependencies to include node-cron for improved scheduling capabilities. * feat(schedule): refactor schedule services and tests for schedule job - Seperate the utils function from schedule service. - Created comprehensive unit tests for all utility functions in `utils.test.ts`, covering various scenarios for cron expression validation, visual picker validation, and schedule resolution. - Ensured proper handling of edge cases and error messages for invalid inputs. * feat(schedule): remove timestamp in schedule tabes to support sqlite - Change the way to update the existing schedule to avoid typescript issue when building. - Add merge function in mockRepo in schedule service test. * fix(schedule): add nullable to optional entity columns and entity interfaces - Add nullable: true to lastRunAt, nextRunAt, endDate on ScheduleRecord entity to match migration DDL and prevent runtime errors - Add IScheduleRecord and IScheduleTriggerLog interfaces to Interface.ts - Have entities implement their respective interfaces per codebase convention * fixed tests and hide schedule input from package/agentflow * feat: integrate IdentityManager into worker and queue management - Remove supporting cron express with 6 fields (second) - Calculate the prediction usage in cron job * feat: add support for MIN_SCHEDULE_INTERVAL_SECONDS in cron job configuration and validation * fixed broken tests * UI UX fixes for scheduler in dark mode * fix(schedule): remove unnecessary UUID generation in createOrUpdateSchedule * adds required scheduleInputMode column with text/form/none variants, ChatType.SCHEDULED, trigger-logs endpoint + drawer UI, IANA timezone dropdown, and dark-mode UX polish. * add deleteScheduleTriggerLogs endpoint and UI integration for log deletion * feat: enhance cron job handling for last day of month (L) in ScheduleBeat and related utilities Co-authored-by: Copilot <[email protected]> * - fix(start-node): persist declared defaults of newly-visible fields so saves don't drop required values - update ui for last day to include hints and next run datetime --------- Co-authored-by: Jackie Chui <[email protected]> Co-authored-by: Henry <[email protected]> Co-authored-by: Copilot <[email protected]>
Flowise Docker Hub Image
Starts Flowise from DockerHub Image
Usage
- Create
.envfile and specify thePORT(refer to.env.example) docker compose up -d- Open http://localhost:3000
- You can bring the containers down by
docker compose stop
🌱 Env Variables
If you like to persist your data (flows, logs, credentials, storage), set these variables in the .env file inside docker folder:
- DATABASE_PATH=/root/.flowise
- LOG_PATH=/root/.flowise/logs
- SECRETKEY_PATH=/root/.flowise
- BLOB_STORAGE_PATH=/root/.flowise/storage
Flowise also support different environment variables to configure your instance. Read more
Queue Mode:
Building from source:
You can build the images for worker and main from scratch with:
docker compose -f docker-compose-queue-source.yml up -d
Monitor Health:
docker compose -f docker-compose-queue-source.yml ps
From pre-built images:
You can also use the pre-built images:
docker compose -f docker-compose-queue-prebuilt.yml up -d
Monitor Health:
docker compose -f docker-compose-queue-prebuilt.yml ps