Integration Nation Icon

Welcome to the new Integration Nation!

Community Questions

Difference Between Trigger and Schedule Fields in SnapLogic Metadata Read Snap and Impact of Updates

·Jun 01, 2026 06:56 AM(edited)·

Hello Team, I am using the SnapLogic Metadata Read Snap to fetch details of a scheduled task. In the output, I noticed two fields—trigger and schedule—both containing similar scheduling information. Could anyone help clarify the difference between these two fields? Additionally, what is the impact of updating either of them using Metadata Update Snaps?

"trigger": {
            "start_date": "2025-05-13",
            "start_time": "16:04:00",
            "time_zone": "UTC",
            "repeat": {
                "blackout_dates": [
                ],
                "by": "minutes",
                "cron": {
                    "month": "*",
                    "day": "*",
                    "day_of_week": "*",
                    "hour": "*",
                    "minute": "0"
                },
                "ends": {
                    "when": "never",
                    "occurrences": null
                },
                "every": 15,
                "on": {
                    "day": [
                    ]
                }
            }
        },
        "schedule": {
            "start_date": "2025-05-13",
            "start_time": "16:04:00",
            "time_zone": "UTC",
            "repeat": {
                "blackout_dates": [
                ],
                "by": "minutes",
                "cron": {
                    "month": "*",
                    "day": "*",
                    "day_of_week": "*",
                    "hour": "*",
                    "minute": "0"
                },
                "ends": {
                    "when": "never",
                    "occurrences": null
                },
                "every": 15,
                "on": {
                    "day": [
                    ]
                }
            }
        }

Scott O.
·
·
Hi Karan – This is a good question, and here's a thorough breakdown based on SnapLogic's task architecture and available documentation: 🔍 Understanding the Two Fields When you use the SnapLogic Read Snap with Asset type = TASK, the output document contains both fields because SnapLogic stores scheduling information at two different layers: 📌 schedule Field This is the SnapLogic-level, UI-friendly representation of the task's scheduling configuration. It reflects what you configured in the Create Task dialog, including: Property Example Start date/time 2025-01-01T09:00:00 Repeat frequency Every 1 day, Every 15 minutes Time zone America/New_York End conditions Never, After N runs, On Date/Time Blackout dates Defined time periods Cron expression Human-readable Cron pattern Think of schedule as the source of truth for the SnapLogic platform — it's what the UI reads and writes. 📌 trigger Field This is the underlying scheduling engine's configuration — SnapLogic uses Quartz Scheduler internally. The trigger field contains the low-level Quartz trigger definition, which may include: Property Description Quartz cron expression The engine-level cron format (may differ from UI representation) Misfire instructions What happens if a trigger is missed (grace period behavior) Next fire time When the trigger is next expected to fire Trigger state Active, paused, etc. Think of trigger as the runtime execution engine's instruction set — it's what actually fires the pipeline. ⚖️ Why Both Exist? They serve different purposes and are maintained somewhat independently: [ SnapLogic UI Schedule Config ] → "schedule" field ↓ (translated/compiled into) [ Quartz Engine Trigger Config ] → "trigger" field In normal operation (creating/editing a task via the UI), SnapLogic keeps these in sync automatically. However, when you read the raw metadata, you see both layers separately. ⚠️ Impact of Updating via Metadata Update Snap This is where you need to be very careful. The official SnapLogic documentation explicitly notes: ⛔ Known Limitation: Trying to use the SnapLogic List Snap along with the Update Snap to alter Task field values causes a 400 HTTP error and doesn't update the Tasks as intended. Here's a summary of risks: Action & Risk Update schedule only The Quartz trigger may become out of sync, potentially causing unexpected firing behavior Update trigger only The SnapLogic UI will display incorrect/stale schedule info; the actual execution may differ from what's shown in Manager Update both High risk of inconsistency unless both are carefully coordinated and formatted correctly Using Metadata Update for Tasks May result in a 400 HTTP error per known limitations of the Metadata Snap Pack ✅ Best Practices & Recommendations
1.
Avoid directly updating trigger or schedule via the Metadata Update Snap for task scheduling changes — these are tightly coupled and prone to causing sync issues.
2.
Use the SnapLogic Manager UI to update task schedules whenever possible, as it handles both fields atomically.
3.
If programmatic updates are required, consider using the SnapLogic REST API directly (via an HTTP Snap) to update task properties, which gives you more control over the full payload.
4.
When reading task metadata for informational purposes, prefer referencing schedule for the human-readable configuration and trigger only if you need engine-level details (e.g., next fire time).
5.
If you need to copy a task's schedule to a new task programmatically, read the full task object without the Normalized checkbox selected to preserve all internal fields.
💡 Pro Tip: When using the SnapLogic Read Snap for tasks, avoid checking the Normalized checkbox, as it strips internal fields that are necessary for creating or updating assets correctly.
Karan C.
·
·
Hey Scott, Thanks for this info. it's really helpful. I couldn't find any documentation related to this, Can you help me with a link?