Topic 16
When Something Goes Wrong
Jena4 makes an interruption visible and gives you a safer next step instead of presenting unfinished work as a successful result.
An uncertain submission
An unclear screen is not a completed action.
Imagine submitting information needed for a release decision and losing the page before a confirmation appears. Do not assume the change failed, and do not assume it succeeded. Jena4 is designed to show when information is unavailable rather than inventing a conclusion. Check the recorded result before submitting the same change again.
First, identify what stopped
Different interruptions need different next steps.
An expired or already-used sign-in email should lead to a new-email path, not a confusing dead end.
A prior result may still be visible while a newer evaluation is pending or has encountered an error.
A safer recovery sequence
Confirm what Jena4 recorded, then use the supported recovery action.
Treat an unavailable page, rejected sign-in, pending evaluation, or visible error as an incomplete experience—not a new conclusion.
Check whether the action already appears in Jena4 before you repeat a write that may have reached the service.
Retry the view, request a new sign-in email, retry the supported action, or ask an authorized owner for help.
Work that takes time
Jena4 keeps unfinished evaluation work distinguishable from a finished answer.
Some decision updates may continue after the page action that started them. Jena4 records whether evaluation is pending, complete, or in error. Where a previous result exists, it can remain visible for context without being presented as a newly completed answer.
When to ask for help
Ask for support when the safe next step does not resolve the uncertainty.
Contact hello@jena4.com if the same problem continues, you cannot reach an authorized workspace, or the recorded result remains unclear. Include the time, the page or action involved, and a non-sensitive error message if one is shown. Never send passwords, sign-in links, or connection secrets.
An important boundary
A recovery step addresses the interrupted action—not every possible outage.
A successful retry does not prove that every connected system responded or that a wider service problem is over. Jena4 should make the state it knows visible; your organization remains responsible for confirming actions in the other systems it operates.