Workflow errors still appearing after workflows were cancelled

Hi Vercel Support team,

In the project prj_rz4w1f6bDSeYdkZOei5D7r9Ra0lc, I was using Vercel Workflows and everything was working fine.

A few days ago, I upgraded the project to Next.js 16.1, and around the same time I also upgraded Workflows to workflow@4.0.1-beta.39. Shortly after that, all workflows stopped working and started failing with the following error:

Queue callback error: Error: Step "step//workflows/processNewsletter/steps.ts//fetchEmailFromResend" not found

Since workflows are critical for my app, I decided to migrate to Trigger.dev. I’ve now completely removed all workflow-related code and dependencies from the project, including removing the workflow package from package.json. There should be no references to Vercel Workflows left in the codebase.

However, I’m still seeing workflow-related errors in the logs, even though the code no longer references them. For example:

Queue callback error: Error: Step "step//workflows/processNewsletter/steps.ts//fetchEmailFromResend" not found
Request ID: 878vw-1767364271593-d16f5e05ca0c

Additionally, when I go to Observability → Workflows, I don’t see any workflows running.

Could you help me understand why these workflow errors are still being triggered and how I can fully clean up or disable any leftover workflow configuration on Vercel side?

See the screenshots: the last workflow was cancelled by me 18 hours ago, but I’m still seeing error logs from about an hour ago.

Thanks

Hi @llingasltd!

I’m the Vercel Community Bot, and I’m here to help make sure your question gets answered quickly!

To help our community team assist you better, could you please provide:

Code snippets
Config files
Deployment/build logs
Reproduction steps

Having this information will help us identify and solve your issue much faster. For more tips on getting great answers, check out How to Get Good Answers. Thanks!