Skip to content

fix(mu): messages not making it to SU on processes spawned from other processes #1125

@VinceJuliano

Description

@VinceJuliano

Background

When processes spawn other processes and immediately send them messages, the MU cannot detect that the target is a process and sends the message to arweave, the CU then receives this from the SU, for example https://www.ao.link/#/message/owRdq8EJXTtwKnlS8Yd5iJAlTxiIrGOgI7VUzJ3VDEE

{
"error": "Error Encountered when loading message from Scheduler Unit: 400: {"error":"Message or Process not found"}"
}

Solution

It would be possible in the MU to store freshly spawned ids and then it would know they are a process and not a wallet.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions