Thank you for providing additional details.
From what we see right now there might be some situations when we are unable to properly reconstruct the execution flow using the information from the log files. This can happen due to a couple different reasons:
- Salesforce might have silently changed something in the logs behavior
- There might be something rare and not-common in terms of your code or execution flow, that we are not handling properly
- There might be some edge-case scenarios when information from debug logs is just plain not sufficient, to reconstruct the flow (for example if your method consists of only one SOQL query, Salesforce does not track method entry and exit in the log file properly)
Taking this into account, there's no option for us, other than asking you to send us a Debug Log file that you're trying to debug. As we completely understand that there might be some kind of sensitive information that you don't want to share (and we don't want to have access to) - if it is suitable for you, please ensure that there's no real data from your org included in the log file, that there's no classes/methods/objects/fields/properties names that you don't want us to see. If there's any kind of such data - we'd kindly ask you to "mask" it in the log file (replace with something similar in terms of data format), so the structure of the log file won't be damaged.
Having this file we should be able to find out any unknown for us situations and will add their support in one of the next releases.
If you're ok to send us the log file - please send it to the email@example.com so it won't be publicly available.