orchestrator
2024.10
true
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Audit
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Managing Non-Working Days
- Triggering jobs on the last day of the month
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Orchestrator User Guide
Last updated Nov 13, 2024
Triggering jobs on the last day of the month
You can choose to execute a job on the last weekday of each month, regardless of the number of days within the month. To do
that, you need to use the
LW subexpression in your cron expression.
59 59 23 LW * ? would trigger at 11:59:59 PM on the last weekday of each month, regardless of whether that day is the 28th or the 31st.
In contrast,
59 59 23 31W * ? would trigger at 11:59:59 PM on the closest weekday to the last day of the month only if the month is 31 days long. In this
case, months that are 28, 29, or 30 days long are skipped.
