What is your goal?
Get my Multi-Agent Pipeline scenario (ID 4712986) running cleanly end-to-end. The scenario should trigger via webhook from a Notion automation, fetch the Notion page properties, filter by tier, and run the rest of the pipeline.
What is the problem & what have you tried?
The execution log shows a Module 5 running that doesn’t exist in the visual designer.
The visual designer shows (left to right): Module 1 (Webhook) → Module 10 (Notion API Call) → Module 19 (HTTP) → Module 65 (Notion API Call, added manually between Module 1 and Module 10) → rest of the scenario.
The execution log shows: Module 1 ✓ → Module 65 ✓ → Module 5 FAILED with 400 Invalid request URL.
A direct GET to /api/v2/scenarios/4712986/blueprint returns a blueprint that includes Module 5 at flow[1] — but the visual designer never shows it, even after logout/login, hard refresh, and closing/reopening the scenario.
The scenario was recently modified via the Make REST API using PATCH /api/v2/scenarios/4712986 with the blueprint as the body. I used Claude Code (Anthropic’s CLI assistant) to call the API directly because the blueprint is ~360 KB and exceeds Windows CLI argument limits. PATCH calls returned HTTP 200 and the verification GET confirmed the changes landed in the API response. Module 65, added manually through the UI, appears correctly in both API and designer. Module 5, added via API PATCH, appears in the API and in the execution log but not in the designer.
I’ve tried: hard browser refresh, full logout/login, closing and reopening the scenario from the scenarios list. The designer never refreshes to show Module 5.
Questions:
Has anyone seen the API blueprint and visual designer diverge like this?
How do I force the designer to refresh from the live blueprint?
How do I delete a module by ID via the API if it’s invisible in the designer?
Is direct PATCH of the scenario blueprint a supported pattern, or should I use a different endpoint?
Error messages or input/output bundles
Module 5 — Notion: Make an API Call
RuntimeError
[400] Invalid request URL.
Screenshots (scenario flow, module settings, errors)
Hey there,
Can you try sharing the scenario?
Hi Stoyan,
Thanks for following up. I’ve attached the full scenario blueprint with credentials redacted.
The key thing I’m hoping you can help with: there’s a Module 5 in this blueprint (a Notion “Make an API Call” module, sitting right after Module 65) that does not appear anywhere in the visual designer. The execution log runs it and it fails with a 400 Invalid request URL, but I can’t see it or edit it in the UI to fix or delete it. I’ve hard-refreshed, logged out and back in, and reopened the scenario — it never shows.
If you look at the blueprint you’ll see Module 5 has the URL /pages/{{1.data.id}} and is missing the metadata block that the other modules have. My question is whether that’s why the designer won’t render it — and more importantly, how I delete a module that exists in the blueprint but not in the UI.
Appreciate any guidance.
Ken
RPA Audit - Multi-Agent Pipeline (Tier 2 & Tier 3).blueprint (1).json (823.0 KB)
Solved — posting the resolution in case it helps someone else.
The phantom module was an artifact of editing the scenario blueprint through the Make REST API (a PATCH that converted the trigger to a webhook). The API write inserted a Notion “Make an API Call” module that the execution engine ran but the visual designer never rendered — because its metadata block was incomplete and it had a malformed URL (missing the /v1/ path prefix). The designer can’t draw a module it can’t fully parse, so it stayed invisible while still executing and failing with a 400.
Because the module didn’t exist in the UI, it couldn’t be deleted from the UI, and a normal designer save wouldn’t flush it either. The fix was to remove it at the blueprint level: pull the scenario via the Make CLI, delete the orphaned module object from the flow array, and PATCH the corrected blueprint back. Verified it was gone by re-pulling and confirming the module ID no longer appears, then confirmed with a clean end-to-end run.
Takeaway: when editing a blueprint programmatically, a module object missing its full metadata/parameters block can execute via the API but never appear in the designer. Worth checking the flow array directly if the execution log shows a module the canvas doesn’t.
Thanks for the help.
I’d say send that to make support as well. They should be made aware of this edge case. It should throw an error message when importing the blueprintnhere.
