Skip to main content
Save a query when you want to run the same report again. Schedule it when you want Yorlet to run the saved query and email a CSV automatically. The Queries tab in the side panel has Saved, Scheduled, and Run history. Click New to start from a blank editor.

​
Save a query

To save a query, follow these steps:
  1. Open Prism.
  2. Write the query, choose a template, or ask the SQL assistant to create it.
  3. Click Run and check that the result is correct.
  4. Click the title and enter a clear name.
  5. Click Save.
If the query already has a name and you have changed the SQL, the button reads Save changes. The Saved list shows queries under By you. Click a query to load it. The subtitle under the title shows when it was saved, and unsaved changes when the editor no longer matches. Use names that explain the scope, such as:
  • Weekly arrears ageing by Building
  • Active Tenancies ending in 90 days
  • Previous month Payment value
  • Open maintenance issues by priority
Save changes replaces the SQL in the saved query. Run and check your changes first, especially when the query has an active schedule.
You must name the query before you can save it.

​
Run history

Run history shows your latest 20 runs from the last 365 days. Each item shows whether it succeeded, failed, or is still running. Click a successful run to load its SQL and result. If it belonged to a saved query, Prism also selects that saved query. Clicking a failed run reloads its SQL so you can fix and run it again, but it does not restore a result. Run history is useful when you:
  • Closed Prism before saving a useful query.
  • Want to compare the SQL from a previous run.
  • Need to return to a failed query and use Fix with assistant.
Save any query you expect to use regularly rather than relying on run history.

​
Schedule a query

A schedule runs a saved query at set times and emails a CSV of the result. Schedules use UTC, so allow for British Summer Time or another local time zone when choosing the hour. Standard allows 5 active schedules. Premium has no cap. To create a schedule, follow these steps:
  1. Run the query and check the result contains only the information recipients should receive.
  2. Save the query.
  3. Click Schedule.
  4. Enter a Cron expression, such as 0 8 * * 1 for every Monday at 08:00 UTC.
  5. Enter Recipients (comma separated).
  6. Click Create schedule.
  7. Check the new schedule under Existing or in the Scheduled list.
Existing schedules for this query appear in the same panel. Click Pause or Resume. The Scheduled list in the side panel also shows Active or Paused, the expression, and how many recipients. Pausing stops future emails without removing the schedule. A paused schedule does not count towards the Standard active schedule limit.
Save the query before you open Schedule. If it is not saved, Prism asks you to save it first.

​
Understand the schedule expression

A cron expression is a short way to describe a repeating schedule. Prism uses five parts:
An asterisk means “every”. Days of the week use 0 for Sunday through 6 for Saturday. Common schedules:
A schedule is not automatically adjusted for daylight saving time. For example, 0 8 * * 1 is 08:00 in the UK during winter and 09:00 during British Summer Time.

​
Change who receives a scheduled report

Prism currently lets you pause or resume an existing schedule. To change its times or recipients:
  1. Open the saved query.
  2. Click Schedule.
  3. Pause the old schedule.
  4. Enter the new expression and recipient list.
  5. Click Create schedule.
Check that the old schedule says Paused so recipients do not receive duplicate emails.

​
Before you schedule

  • Use a relative period such as “previous complete month” if the report should move forward automatically.
  • Avoid a fixed date unless you intentionally want the same period every time.
  • Give the query a name that will make sense in an email.
  • Keep recipient addresses current.
  • Include only the personal and financial information each recipient needs.
  • Check Data as of so you understand when the snapshot refreshes relative to the schedule.
  • Run the query manually after changing its SQL.