Deferred call context error

[modship]

When the execution of the deferred call fail we need more information about the fail in the event generated in the context of the caller SC.

[HahaZaineb]

I second this,
I am developing a vesting smart contract on the Massa blockchain using Deferred Calls. Despite successful contract deployment and token locking, I encounter persistent errors related to deferred call execution in the releaseVestedTokens function (Repo) .

Expected Behavior

• The vesting schedule should be stored and retrievable from storage during ReleaseVestedTokens execution.
• Deferred calls to ReleaseVestedTokens should execute successfully at scheduled periods, transferring tokens to the beneficiary.

Current Behavior

• Deferred calls fail with "DeferredCall execution fail call_id" errors, often showing "beneficiary cannot be empty" or "data entry not found" runtime errors.
• The deferred call appears to be registered successfully, but its execution consistently fails, and there are no ways to obtain more detailed information about the failure for effective debugging.

Additional Context

• Serialization/deserialization has been verified, and extensive logging added, yet the errors persist.
• Can you suggest debugging steps or solutions to resolve these failures and improve error reporting for deferred call issues?

Else, we do need more information about the fail in the event generated.