Automated Panoply Data Load Reconciliation
Every morning, WebRun opens Panoply, checks the load status of every connected data source from overnight, posts a summary of any failed or stale load to Microsoft Teams naming the source and the error, and creates a Trello card for each one so the warehouse team has a running list of what needs fixing before reports run on incomplete data.
How do I confirm my overnight Panoply data loads actually completed?
WebRun checks every connected source in Panoply each morning for a failed or stale overnight load. Any broken source gets posted to Microsoft Teams with its error and a Trello card to track the fix, so the warehouse team catches a dead data feed before a report or dashboard quietly runs on incomplete data.
- Broken data loads get caught before a report is built on stale data
- The team works from a running Trello list of exactly what needs fixing
- A clean night still gets a confirmation posted to Teams
Built for Data engineering teams · Data analysts · BI teams · Data platform teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
panoply.ioin a real browser with your saved login - no setup, no API keys. -
1
Panoply - check overnight load status
panoply.io
WebRun opens Panoply to check overnight load status. - Open Panoply and check the last load status for every connected source
- Flag any source that failed its last load or has not refreshed in 24 hours
- Note the error message where available
Done when Every connected source has been checked for a failed or stale load.
-
2
Microsoft Teams - post failed loads
microsoft.com
WebRun opens Microsoft Teams to post failed loads. - Post the failed or stale sources with their errors to the data team channel
- Sort by how long each has been down
- Send a short all clear if nothing failed
Done when The data team channel has today's load status summary.
-
3
Trello - log a fix card per source
trello.com
WebRun opens Trello to log a fix card per source. - Create a card for each broken source on the warehouse health board
- Include the source name, the error, and how long it has been down
- Move a card to done once its source loads successfully again
Done when Every currently broken source has an open Trello card.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun reload the data itself?
No. It only detects and reports the failure. Reloading a source or fixing its connection stays with your data team.
What counts as a stale load?
Any connected source that has not completed a successful load in the last 24 hours, or whose last attempted load failed outright.
Does the Trello card close automatically once fixed?
Yes. Once a source loads successfully again, WebRun moves its card to done on the next check, so the board only shows what is still broken.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.