Automation · Operations and reporting

Check on WhatsApp why your app's deployment failed on Prisma Compute

Ask on WhatsApp why your app is not responding: an AI agent checks the builds, the deployments and the latest one's logs in Prisma Compute.

Show me this with my own operation See every automation

How do I know why my app's last deployment on Prisma Compute failed without opening the console?

You write to your Met "the app is not loading, what happened with the deployment?". The Met confirms the connected Prisma workspace, finds your app on Prisma Compute, lists the latest builds with their state and the app's deployments, and reads the runtime logs of the latest deployment. It replies with what it found: whether the build failed, which deployment is the most recent and which error shows up in the logs. Everything is read-only: the Met does not promote, roll back or stop deployments in this procedure.

What starts it

When someone asks for it

It starts when someone on the team asks the Met on WhatsApp why the app is not responding. Each check runs on request; the Met does not watch deployments on its own.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Internal Met that checks your Prisma Compute apps

This is not a named, seeded Met. It is an internal Met with Prisma connected, for the owner or the agency that maintains the app: its work ends when it tells you what it found in the builds, the deployments and the logs.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

Prisma Postgres Automate and collaborate

5 steps · 5 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Confirm the workspace

The Met brings the details of the connected Prisma workspace to confirm it is looking at your business's workspace.
- fetch_workspace_details Prisma Postgres
2
Find the app

The Met lists the workspace's Prisma Compute apps and takes the one named in its instructions, filtering by project if you have several.
- list_prisma_compute_apps Prisma Postgres
3
Check recent builds

The Met lists builds from newest to oldest, filtered by the main branch, to see whether the latest one finished or failed.
- list_prisma_compute_builds Prisma Postgres
4
Check the deployments

The Met lists the app's deployments, newest first, to know which one is the most recent and what state it ended up in.
- list_prisma_compute_deployments Prisma Postgres
5
Read the logs and reply

The Met reads the latest deployment's runtime logs, page by page, and replies with the error that repeats and what it saw in the builds and deployments.
- get_prisma_compute_deployment_logs Prisma Postgres

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

Prisma connected in Met

In Met, open Connections → Prisma Postgres → Connect, sign in to Prisma and choose the workspace where your app lives.
An internal Met on WhatsApp

Assign the connector to a Met that only serves the team, not the one that talks to customers, because the same connection brings actions that stop deployments, run SQL and delete resources.
The app and branch in the instructions

Write in the Met's instructions which Prisma Compute app is yours and its main branch, so it always checks the right one.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not fix the outage. The Met tells you what it found; fixing the code and redeploying is your team's work.
It does not go back to a previous version in this procedure. Rolling back or promoting a deployment are actions in the listing that this procedure does not use.
It does not see failures outside Prisma Compute, such as an expired domain or a down external service. The logs only show what happens inside the deployment.
It does not alert you on its own when a deployment fails. The check starts when someone asks the Met.

FAQ

Questions about this automation

The listing has the action that rolls the app back to an existing deployment, but this procedure does not use it. It starts turned off: if the admin turns it on in Connections, you ask for it in another instruction.

No. Prisma says the Compute tools manage existing apps and deployments and do not build or upload your code.

Yes, it is the same connection. This procedure only looks at the app; checking the database or its backups is another question for the Met.

Keep going