My script runs perfectly sometimes, but sometimes it returns as null for all nodes

Revit
21

1.rvt (4.4 MB)

Terminal Connections - Connectors Universal.dyn (365.3 KB)

to add a note. this script is for automatic modelling of flex pipes.

this code only does for one equipment to another
when this issue is fixed, i have to modify this script to fit for series of equipments

22

Are you sure this Dynamo log and Revit journal correlate? The Revit journal indicates a total session time of about 6 minutes while the Dynamo log indicates about 30 minutes of activity.

Also, be sure to restart the CPU before recreating - another Revit instance might not have shut down a shared component correctly which could be causing the issue.

23

journal.0472.txt (289.2 KB)

dynamoLog_74557369-d929-40fa-bd43-c6375b9ff2d7.txt (13.7 KB)

kindly check if this is ok

24

Seem to be a missmatch stillā€¦ letā€™s try this.

  1. Close all your applications.
  2. Delete everything your Dynamo logs folder.
  3. Delete everything in your Revit journalā€™s folder.
  4. Start Revit, launch Dynamo, and recreate the issue.
  5. Force quit Revit.
  6. Post the only journal in the folder (if you see more then one, restart at step 2).
  7. Post the only Dynamo log in the folder (if you see more than one, restart at step 2).
25

journal.0001.txt (238.3 KB)

dynamoLog_7f30dfe8-76b3-4a40-a71d-c752438cbb69.txt (13.2 KB)

please check now @jacob.small

26

Those align - Iā€™m tied up for the rest of the work day now though, but will try and have a look when I can.

1 Like
27

i just took a fast look, a lot of custom packages in use, you are sure all is up to date and maybe not give conflict..i dont say thats the issue, but worth to check

29

Hereā€™s an old topic of mine on the same issue: Nodes stop working randomly

The cause for this behavior was never found. Again, the only thing that ever worked for me was recreating the graph, hopefully through as much copy / pasting as possible.

One possible cause I could think of was a tiny ms connection failure for graphs, stored on a network location. At least in my case, it was always happening with scripts that are not stored locally.

1 Like
30

Hi @danail.momchilov
yeah have thhat issue in older version, and the only thing was copy the graph to a new fresh, that worked for meā€¦but havent seen it since 2022 i guessā€¦and seems @Kashyapras is in 24ā€¦yeah you are probably right with thisā€¦not stored locally

1 Like
31

Iā€™ve had similar issues off and on, especially with 3rd-party packages. Instead of recreating (copy & pasting) the graphs I can normally just save it, reopen it and rerun it with some success. Itā€™s honestly my first step in solving an unknown error at this point lol.