Documentation Index
Fetch the complete documentation index at: https://docs.markifact.com/llms.txt
Use this file to discover all available pages before exploring further.
The Schedule Trigger automatically executes workflows at specified intervals, enabling powerful automation and recurring tasks. Set up workflows to run daily, weekly, monthly, or at custom intervals without manual intervention.
When to Use It
- Automate recurring reports and data processing
- Schedule regular data backups and syncing
- Run maintenance tasks and cleanup operations
- Generate periodic notifications and alerts
- Execute time-sensitive business processes
- Automate social media posting and content updates
- Process batch operations at optimal times
Schedule Types
| Schedule Type | Description | Use Cases |
|---|
| Daily | Runs once per day at specified time | Daily reports, backups, notifications |
| Weekly | Runs weekly on specified day/time | Weekly summaries, team updates |
| Monthly | Runs monthly on specified day/time | Monthly reports, billing cycles |
| Hourly | Runs every X hours with minute offset | Frequent data syncing, monitoring |
| Minutely | Runs every X minutes | Real-time processing, alerts |
| Once | Runs one time at specific date/time | One-off tasks, event triggers |
Configuration Options
Daily Schedule
| Field | Type | Description | Example |
|---|
| Interval | Select | ”daily” | Daily execution |
| Run Time | Time | Time of day (HH:MM) | “09:00” (9:00 AM) |
Interval: daily
Run Time: 14:30
Result: Runs every day at 2:30 PM
Weekly Schedule
| Field | Type | Description | Example |
|---|
| Interval | Select | ”weekly” | Weekly execution |
| Week Day | Select | Day of week (0-6) | “1” (Monday) |
| Run Time | Time | Time of day (HH:MM) | “10:00” (10:00 AM) |
- 0 = Sunday
- 1 = Monday
- 2 = Tuesday
- 3 = Wednesday
- 4 = Thursday
- 5 = Friday
- 6 = Saturday
Example:
Interval: weekly
Week Day: 1 (Monday)
Run Time: 09:00
Result: Runs every Monday at 9:00 AM
Monthly Schedule
| Field | Type | Description | Example |
|---|
| Interval | Select | ”monthly” | Monthly execution |
| Month Day | Number | Day of month (1-31) | “15” (15th of month) |
| Run Time | Time | Time of day (HH:MM) | “12:00” (Noon) |
Interval: monthly
Month Day: 1
Run Time: 08:00
Result: Runs on the 1st of every month at 8:00 AM
Hourly Schedule
| Field | Type | Description | Example |
|---|
| Interval | Select | ”hourly” | Hourly execution |
| Hours | Number | Every X hours (1-23) | “6” (every 6 hours) |
| Hour Offset | Select | Minute offset (0,15,30,45) | “30” (XX:30) |
Interval: hourly
Hours: 4
Hour Offset: 15
Result: Runs every 4 hours at 15 minutes past (02:15, 06:15, 10:15, etc.)
Minutely Schedule ⭐ Premium Feature
| Field | Type | Description | Example |
|---|
| Interval | Select | ”minutely” | Minute-based execution |
| Minutes | Number | Every X minutes (1-59) | “30” (every 30 minutes) |
- Premium users: Can use 1-59 minutes
- Standard users: Minimum 15 minutes
- Free users: Not available
Example:
Interval: minutely
Minutes: 15
Result: Runs every 15 minutes
One-Time Schedule
| Field | Type | Description | Example |
|---|
| Interval | Select | ”once” | Single execution |
| Once Time | DateTime | Specific date and time | ”2024-03-20 14:30:00” |
- Must be at least 15 minutes in the future
- Cannot be in the past
- Automatically deactivates after execution
Example:
Interval: once
Once Time: 2024-03-20 15:00:00
Result: Runs once on March 20, 2024 at 3:00 PM
Credit Cost
- Trigger activation: 0 credits (Free)
- Workflow execution: Credits charged based on nodes used in workflow
- Schedule management: No additional cost
Schedule Management
Activation and Deactivation
- Automatic activation - Schedules activate when workflow is published
- Manual control - Can be paused/resumed through workflow settings
- Automatic deactivation - “Once” schedules deactivate after execution
- Error handling - Failed runs don’t stop future scheduled executions
Timezone Handling
- Browser timezone - All schedule times use your browser’s current timezone
- Automatic detection - Timezone is automatically detected from your browser
- Daylight saving - Automatically adjusts for DST changes
- Global teams - Consider team member timezones when scheduling
- Time display - UI shows times in your browser’s timezone
Execution Monitoring
- Run history - View all scheduled executions in workflow logs
- Success/failure tracking - Monitor execution status and errors
- Performance metrics - Track execution time and resource usage
- Alert setup - Configure notifications for failed runs
Troubleshooting
Common Issues
Schedule Not Running:
- Check if workflow is published and active
- Verify schedule configuration is complete
- Ensure all required fields are filled
- Check account permissions and credit balance
Unexpected Execution Times:
- Verify timezone settings
- Check for daylight saving time effects
- Review schedule configuration parameters
- Consider server processing delays
Failed Executions:
- Review workflow error logs
- Check for API rate limits
- Verify connection credentials
- Ensure adequate credit balance
Performance Issues:
- Optimize workflow efficiency
- Reduce concurrent scheduled workflows
- Consider less frequent scheduling
- Monitor system resource usage
