HTTP Request blocks lose their request references after periods of inactivity + module call failures on Cloud

Hey Team,

Every few weeks when I return to my Postman Flows, HTTP Request blocks show “Failed to load request” — even though the requests still exist in my collection. I have to manually re-select the correct request in every affected block before I can run the flow again.

Key details on the reference issue:

  • Reproducible on desktop app
  • Happens after a few weeks of not opening the flow
  • Collection requests are intact; only the block-level references break
  • Affects multiple blocks per flow, not isolated to one
  • Every time need to select environment, variables in the request

Separately, I’ve also noticed that for deployed Flows on cloud, flows calling a module fail — even though the module itself runs fine standalone. The same module works in isolation but breaks when invoked as a subflow from a parent flow.

Together, these two issues make Flows unusable as a serious automation tool. For a small number of flows I can manually fix references and debug module failures, but scaling to 50–100+ HTTP Request blocks across multiple flows with module dependencies is not feasible when things silently break.

Could the team please investigate both issues and confirm whether fixes are planned?

SS of Issue 1 -

SS of Issue 2 -

Thanks for reporting these issues — sorry you’re encountering this.

Two questions; are you on the latest app version? Given that it happens after a while, I’m wondering if it’s related to app upgrade or if you’re on the same version between opens. Just fishing for a clue to help us diagnose.

On the second issue, this is usually an error in logic. Does the module for example fail to handle an error case, there’s some path that is usually not handled under composition. Have you looked at the run logs to drill into the module steps and see where the issue occurred? If it helps happy to look into this one together.

Hi @lunar-module-1

To ans your questions -

  1. Yes I am on the lates app version
  2. I could have opened flows after two updates.
  3. Second issue shouldn’t be because of error in logic why because the first block after request block is calling a module SS#3 which is working perfectly fine on its own SS#4. After Start block I am expecting module to return some data and nothing else whether it is successful or failed.

Thanks for the clarifications - we’re investigating the first issue.

For the failed module run, have you looked the run logs to drill into the module and see why it failed?

The run logs traces are also available in the flows analytics view if they were triggered automatically.

These should show you where in the module the error occurred and why.

One clue I see from your screen shot, your variables are not pinned — is the module invocation part of a loop? If so, recommend pinning the variables. It could be the module is not getting any input for example. If you can share more of the flow we can help you more effectively.

If the screenshot is more or less the entire flow, then please look through the runlogs and share what you find. If it’s faster feel free to dm or open a support ticket and we can take a look together.

HI @lunar-module-1 ,

Issue is happening whenever I am pushing new changes from my local to postman cloud. Because of this I have to reset everything again which is very frustrating.

  1. I create/update a flow merge it in my bitbucket repo.
  2. Push the whole workspace to postman cloud
  3. Switch to cloud
  4. Pull the whole workspace again
  5. Try to run Flow
    1. How my scripts work → Request Block → Common Module (HTTP request, returns pass/fail output using OR) → Evaluate block runs validation → Response/Display.
  6. Issue that I get is “An error occurred while executing the flow”

Main Flow/Test Script -

Common Module -