Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Environment

Alpha Dev Roxie

Description

None

Conclusion

None

Activity

Show:

Gavin Halliday February 19, 2021 at 5:52 PM
Edited

Also https://github.com/hpcc-systems/HPCC-Platform/pull/14600 reversing the change that defaulted some strict checking on.

 

Gavin Halliday February 12, 2021 at 12:11 PM
Edited

Some information from the query:

Actiivty 7710 is a stored result, the last activity in the graph

Activity 7287 is the first activity in the graph

It suggests that either an exception was thrown during reset(), or a stop() on a splitter caused the input to be moved from reset to started.

If an exception wasn't thrown during reset() then activity 7710 for example would be reset - so it seems very likely to be a problem with reset()

Kevin Logemann February 11, 2021 at 5:18 PM

I think Gavin has the archive he needs, but if you need a ZAP file or anything else, let me know.

Gavin Halliday February 11, 2021 at 1:40 PM

 which esp are the workunits on?

 

Richard Chapman February 11, 2021 at 11:57 AM

Not sure this is SOAPCALL at fault directly, but one of the other activities on the chain. I probably need a ZAP file and/or archive

Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash 1JOJMU2 Trace 357ae05d2b5943a7a7222d0f4bd5fdb4
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Richard Chapman

Reporter

Kevin Logemann

Priority

Not specified

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/14591

Affects versions

Flag notifications