We have a Revit model that doesn't seem to be running in Forge. It runs just fine in our local Revit Plugin, but it seems to 'hang' when trying it in Forge. After 3 hours, Forge just times-out...
The model isn't that big (less than 150MB), and we've handled many different (and larger) models before with success.
The logs from Forge doesn't tell us that much. It seems that the code from out plugin did not even run (we log the start of our code). Is there a way to get access to the journal file from Forge? Or is there an other way to see what might be the cause?
...
[05/03/2021 14:32:10] Initialize and get RCE: (VersionBuild) 21.1.20.44 (VersionNumber) 2021 (SubVersionNumber) 2021.2
[05/03/2021 17:31:52] Error: Revit Core Engine Core Console is shut down due to process time limit.
[05/03/2021 17:31:52] End script phase.
[05/03/2021 17:31:52] Error: An unexpected error happened during phase CoreEngineExecution of job.
[05/03/2021 17:31:52] Job finished with result FailedLimitProcessingTime
the workitemid:b27223519e824cdc90df80a1af6e718b
The issue is reproducible. So if you like we can send the model again and it will do exactly the same.
Related
Getting this error
I have all the necessary tokens included in the yaml.
The code ran with no issues before.
Check if the issue persists considering there were an outage on GitHub side (regarding Codespace), while there was no recent incident on Terraform Cloud.
The first one might have an incidence on accessing the second one.
Im developping a plugin for AutoCAD on Forge. Via a custom command (Provided by the plugin), it will publish a big png (25000x20000 for example) and sometimes it causes a timeout and the workitem failed.
<report.txt>
...
[03/02/2022 22:10:41] Save changes to page setup [Yes/No]? <N> N
[03/02/2022 22:10:41] Proceed with plot [Yes/No] <Y>: Y
[03/02/2022 22:10:41] Effective plotting area: 21212.94 wide by 20000.00 high
[03/02/2022 22:10:41] Plotting viewport 2.
[03/02/2022 22:11:42] Error: AutoCAD Core Console is shut down due to timeout.
[03/02/2022 22:11:42] End script phase.
[03/02/2022 22:11:42] Error: An unexpected error happened during phase CoreEngineExecution of job.
...
Im guessing the timeout will be done by design (Work Item Heartbeat) but havent succeed to find the way to make the long plotting survive.
Is there anyone who can help me?
The suggested solution, HeartBeat.cs has been tried but it seems not working for my case (because the engine Im using is AutoCAD?) though the document said that it will be ok if my plugin will print something (to stdout(=report.txt?) or trace(the suggested one) before one minute silence.
Additionally the actual PLOT command is issued on a scr file which is loaded and is executed inside my plugin.
PS1.
The only way to print something on report.txt I find is
Document doc = Application.DocumentManager.MdiActiveDocument;
doc.Editor.WriteMessage("somthing");
and seems the doc doesnt work with threading.
PS2.
The limitProcessingTimeSec for the workitem has been changed to 300, but it seems not related.
we are experiencing errors in the latest version (7.55) of the forge viewer. When loading a Revit model, the following error displays in the browser console:
Failed to load model: New Construction. Error code: TypeError: e.target.clone is not a function
This is an SVF2 model that was translated using the generateMasterViews flag. New Construction is one of the master views names in this particular model.
I had a hunch this was due to the new update, so I downgraded our version from 7.55 to 7.54. After downgrading the issue no longer occurred. Was there a breaking change in 7.55 that we need to be aware of? I did not see anything in the changelog
Forge Viewer uses Semantic Versioning so none of the "minor" version updates should be breaking, but it could be some regression. In the call stack I see you're using AggregatedView. Have you tried loading your model in a simple Viewer3D or GuiViewer3D instance instead of that one? And could you share more details about how you're initializing the viewer and loading the models into it?
I am new to the Design Automation API, so please excuse and correct me if I am using the wrong terms. I am setting up the wiring for my very first Design Automation AppBundle, and I have almost all of it working. I followed the patterns in the "Delete Walls" tutorial.
I have a working add-in DLL that I can test locally and it runs under the "design.automation-csharp-revit.local.debug.tool".
I also have all of the Rest API connections setup, and I can successfully submit a WorkItem that will download a Revit file from a BIM 360, and start processing it in the sandbox of Design Automation. But I am getting an error during the execution on the sandbox where it seems it can't find my add-in file. Here is an excerpt from the WorkItem log:
[07/21/2020 18:02:26] Resolving location of Revit/RevitCoreEngine installation...
[07/21/2020 18:02:26] Running user application....
[07/21/2020 18:02:31] Cannot find the addin file:
[07/21/2020 18:02:31] Fail to deploy Addon DLL(s) in AppPackages.
[07/21/2020 18:02:31] RESULT: Failure
I have looked through "bundle" ZIP file many times looking for typos that could cause this, but I can't find anything, it looks identical to the "delete walls" example. So I'm wondering if there is somewhere else that I need to look. Or any other way I could debug this to find out were the connection is missing. I can only assume that the AppBundle and Activity items are setup correctly since I am getting this far and the error is not mentioning either of those items.
Any tips on where to look?
This turned out to be a misspelling of the [dot]bundle folder extension that triggered the issue.
I ran a model derivative job and the status came back: failed. After drilling through the return values, it said that two of the linked dwg files were missing. I added the dwg files, re-zipped and re-uploaded the zip. When I try to run the job, it keeps coming back with the initial failed status. Am I missing something?
Assuming you have buckets, on the POST Job endpoint, use the x-ads-force header, if you pass true it will translate again the file.
In hindsight, one could say this is obvious but it isn't spelled out in any documentation anywhere. Essentially, one needs to DELETE the failed manifest and run a new job. There doesn't seem to be any re-try mechanics.