Qlik Cloud reload failure triage agent

Build me an agent workflow that triages Qlik Cloud reload failures on a schedule and routes them to Slack and ServiceNow.

Trigger: a cron schedule that runs once an hour during business hours (default Monday to Friday, 7am to 7pm in my local time zone). Persist the timestamp of the last successful run so each invocation only considers reloads that finished after that point.

On each run, do the following:

1. Determine the set of Qlik Cloud apps to watch. Accept a configurable list of app IDs as input. If the list is empty, fall back to every app the account can see by calling List Apps in Qlik Cloud.

2. For each app in scope, call List Reloads in Qlik Cloud and filter to reloads whose status is FAILED or CANCELED and whose end time is after the last run timestamp. Skip reloads that are still QUEUED or RELOADING.

3. For each failed or canceled reload, call Get App Details in Qlik Cloud to fetch the human-readable app name and owner. Capture the reload ID, end time, duration, and any error log or message available on the reload record.

4. Write a short triage note per failure (3 to 6 lines) that includes:

- The app name and a link back to the app in Qlik Cloud.

- When it failed (in the user's local time zone) and how long it ran.

- Final status (FAILED or CANCELED) and the reload ID.

- The most likely cause inferred from the error text. Pick from categories like script error, source connectivity, permissions, timeout, missing field or table, license or capacity, or unknown.

- One concrete "what to check first" suggestion tied to that likely cause.

5. Post each triage note to a configured Slack channel (default #data-platform) by calling Send a Message in Slack Bot. Use Slack mrkdwn formatting. Group multiple failures from the same run into a single message if there are more than three, with each failure as its own short section.

6. For any failed reload on an app whose ID appears in a configurable businessCriticalAppIds list, also call Create Incident in ServiceNow. Set:

- short_description: "Qlik reload failed: <app name>"

- description: the full triage note plus the Qlik app link and failed reload ID.

- priority: configurable, defaulting to 2 (High) for business-critical apps.

- category: "Software" and a configurable assignment_group for the data platform team.

After creating the incident, append the incident number back into the Slack message so the team can click straight through.

7. If no failures were found since the last run, exit silently without posting to Slack or opening a ServiceNow incident.

8. After a successful run, update the stored last-run timestamp to the current time so the next invocation picks up only new failures.

Inputs the workflow should expose:

- watchedAppIds: optional list of Qlik app UUIDs (empty = all apps).

- businessCriticalAppIds: optional list of Qlik app UUIDs that escalate to ServiceNow.

- slackChannel: target channel name or ID (default #data-platform).

- serviceNowAssignmentGroup: assignment group for created incidents.

- defaultIncidentPriority: integer 1 to 5, defaulting to 2.

- timezone: IANA time zone for schedule and timestamps.

Tone for the triage note: calm, factual, no marketing language, no emojis beyond a single status indicator. The note should read like an on-call summary, not a slack rant.