jasquat
jasquat
@burnettk possibly due to rjsf upgrade?
Closing for now since we may no be going this route.
I found an "extra" `` line in the xml. When I commented it out it seemed to work: https://dev.app.spiff.status.im/process-instances/for-me/misc:qa:bpmn-model-testing:unit-test-escalation-event/1815 I'm not sure how that extra sequenceFlow got in there or...
I don't think you have to do a force refresh, it just takes a long time to load. We could add a loading icon there and load the page before...
Yeah the time it takes to load will depend very much on how many tasks are associated with a process instance. The PR mentioned above keeps it from loading all...
One way to do this may be to create a new tab under the "Process Instances" main nav item to view error events. We could leverage the code for log_list...
@madhurrya the full url is https://dev.app.spiff.status.im/extensions/recent-error-events. This is an extension and needs to be run as an extension rather than from starting the model. We did add a ui component...
Yep, and yeah. We are looking into fixing the markdown sensitization to fix this.
@madhurrya it should be working now.
@madhurrya I think it's working as expected. We do not query process instances. Instead we query the error events that are attached to them. For process instance 33, there are...