You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c145bf5
Browse filesBrowse the repository at this point in the historyBrowse files
If your Next.js app has a [proxy handler](https://nextjs.org/docs/app/api-reference/file-conventions/proxy)
85
85
(formerly known as "middleware"), you'll need to update the matcher pattern to exclude Workflow's
86
86
internal paths to prevent the proxy handler from running on them.
87
87
88
-
Add `.well-known/workflow/*` to your middleware's exclusion list:
88
+
If you see `[local world] Queue operation failed` with `Cannot perform ArrayBuffer.prototype.slice on a detached ArrayBuffer`, your proxy matcher is still intercepting Workflow's internal `POST /.well-known/workflow/v1/flow` request. This is especially easy to miss in Next.js 16, where `proxy.ts` replaced `middleware.ts`.
89
+
90
+
Add `.well-known/workflow/*` to your matcher exclusion list:
If your Next.js app has a [proxy handler](https://nextjs.org/docs/app/api-reference/file-conventions/proxy)
85
85
(formerly known as "middleware"), you'll need to update the matcher pattern to exclude Workflow's
86
86
internal paths to prevent the proxy handler from running on them.
87
87
88
-
Add `.well-known/workflow/*` to your middleware's exclusion list:
88
+
If you see `[local world] Queue operation failed` with `Cannot perform ArrayBuffer.prototype.slice on a detached ArrayBuffer`, your proxy matcher is still intercepting Workflow's internal `POST /.well-known/workflow/v1/flow` request. This is especially easy to miss in Next.js 16, where `proxy.ts` replaced `middleware.ts`.
89
+
90
+
Add `.well-known/workflow/*` to your matcher exclusion list:
0 commit comments