Monitor Journal Entries

Monitor Journal Entries

Journal Monitor lets you watch a selected Feluda journal for new entries in real time.

It is useful when a conversation, workflow, or scheduled process is expected to write information to the Journal.

Instead of refreshing the Journal repeatedly, you can keep the monitor open and see when a new entry appears.

Journal Monitor helps you:

• notice new entries;
• follow long-running workflow activity;
• watch recurring reports arrive;
• compare entry times;
• identify missing or duplicate results; and
• decide when further review is needed.

The monitor shows that new content was written.

It does not confirm that the content is correct.

When to use Journal Monitor

Journal Monitor is useful when:

• a workflow writes several entries over time;
• a scheduled workflow creates recurring reports;
• a long-running process records progress;
• several AI agents may write findings;
• you are waiting for a specific result;
• a research process adds new notes; or
• you need to confirm that a Journal write occurred.

You do not need to keep Journal Monitor open for every Journal entry.

Use it when real-time awareness adds value.

Before you begin

Confirm that:

• Feluda is open;
• the expected journal exists;
• the workflow or AI tool can write to that journal;
• required providers and tools are available;
• the workflow has been tested; and
• you know what kind of entry should appear.

Use non-sensitive test information when monitoring a new process for the first time.

Open Journal Monitor

Open Journal from the Feluda sidebar.

Then open Journal Monitor using the available control.

Select the journal you want to watch.

The monitor begins watching that selected journal for new entries.

Keep Feluda open while active monitoring is needed.

Choose the correct journal

Make sure you select the journal used by the workflow or AI tool.

Before monitoring, confirm:

• the journal name;
• the workflow destination;
• the expected entry title;
• the approximate run time;
• whether the entry is created manually or automatically; and
• whether another workflow writes to the same journal.

Monitoring the wrong journal can make a successful workflow appear to have failed.

Know what entry to expect

Define the expected result before the process starts.

For example, a weekly project workflow may create:

Weekly Project Review — 2026-W23

A daily monitoring workflow may create:

Daily Monitoring Summary — 2026-06-08

Clear titles make new entries easier to recognise.

A title such as "Report" is difficult to distinguish from earlier entries.

Start the related process

The entry may come from:

• a Workbench conversation;
• an on-demand RunFlows execution;
• a scheduled workflow;
• a manual Journal note;
• a Gene-provided flow; or
• another supported Journal-writing action.

Start or wait for the relevant process.

Keep Journal Monitor visible when you need to see the result as soon as it appears.

Watch for new entries

When a new entry is written to the selected journal, it should appear in the monitor.

Review:

• the title;
• the timestamp;
• the source or workflow;
• the entry content;
• whether the entry arrived at the expected time; and
• whether more than one entry appeared.

A new entry may be a final result, an intermediate update, or an error note.

Open it before deciding what it represents.

Check the timestamp

The timestamp helps you match the entry to a specific run.

Compare it with:

• the Workbench activity time;
• the RunFlows start and completion time;
• the scheduled trigger time;
• the expected reporting period; and
• other entries created around the same moment.

A timestamp can help distinguish a new entry from an older entry with a similar title.

Open and review the full entry

Do not rely only on the title shown in the monitor.

Open the entry and check:

• whether the full content was saved;
• whether important facts match the source;
• whether missing information is visible;
• whether the entry uses the expected structure;
• whether links and tables display correctly;
• whether unsupported claims were added; and
• whether human approval is needed.

Journal Monitor notices activity.

Human review determines whether the result is useful.

Monitor a Workbench Journal action

When using the Journal tool in Workbench:

1. open Journal Monitor;
2. select the intended journal;
3. return to Workbench;
4. enable the Journal tool;
5. ask the model to create the entry;
6. review the Workbench Activity log;
7. return to Journal Monitor; and
8. open the new entry.

Confirm both the tool activity and the saved result.

The model saying that an entry was created is not enough.

Monitor an on-demand workflow

For a workflow started through RunFlows:

1. open Journal Monitor in the selected journal;
2. start the workflow in RunFlows;
3. watch the workflow output;
4. confirm that it reaches the Journal step;
5. watch for the new entry;
6. compare the timestamp with the run; and
7. review the full content.

Use RunFlows to understand the execution.

Use Journal Monitor to confirm that the entry arrived.

Monitor a scheduled workflow

For a scheduled workflow:

• confirm the next-run date and time;
• confirm the timezone;
• keep Feluda and required services available;
• open Journal Monitor when real-time observation is needed;
• select the correct journal;
• wait for the planned run;
• check Schedule Manager history; and
• review the new entry when it appears.

The schedule history confirms whether the workflow ran.

Journal Monitor confirms whether the selected journal received a new entry.

Use Journal Monitor with long-running workflows

A long workflow may create entries at different stages.

For example:

Start Research
→ Write Initial Sources
→ Analyse Findings
→ Write Final Summary

Journal Monitor can help you see when each entry arrives.

Make sure titles explain the stage.

For example:

• Research Sources — 2026-06-08;
• Research Findings — 2026-06-08;
• Research Final Summary — 2026-06-08.

Clear stage names prevent intermediate entries from being mistaken for the final result.

Use Journal Monitor with several agents

Several AI agents or workflow branches may write to one journal.

Use titles that identify:

• the agent;
• the task;
• the stage;
• the source;
• the project; or
• the reporting period.

For example:

Research Agent — Source Review — 2026-06-08

is clearer than:

New Findings

When several entries arrive close together, compare titles and timestamps carefully.

Distinguish progress entries from final entries

A progress entry may show:

• collected sources;
• extracted fields;
• an early classification;
• a partial report;
• a checkpoint; or
• a warning.

A final entry should clearly identify that the process is complete.

Use title words such as:

• Progress;
• Draft;
• Interim;
• Final;
• Completed; or
• Needs Review.

Do not treat an interim result as final output.

Use clear recurring titles

Recurring workflows should create unique entries.

Include a:

• date;
• week;
• month;
• run identifier;
• project;
• region; or
• reporting period.

Good examples include:

• Daily Briefing — 2026-06-08;
• Weekly Support Review — 2026-W23;
• Monthly Risk Summary — June 2026.

Unique titles make monitoring and duplicate detection easier.

Check for duplicate entries

When two similar entries appear, compare:

• titles;
• timestamps;
• workflow names;
• schedule history;
• active runs;
• content; and
• tool activity.

Duplicates may be caused by:

• the same workflow running twice;
• overlapping schedules;
• an immediate retry after a timeout;
• two workflows writing to the same journal;
• a manual and scheduled run; or
• a delayed confirmation.

Pause related schedules before investigating repeated duplicates.

Check for missing entries

When an expected entry does not appear, confirm:

• the correct journal is selected;
• the workflow or conversation ran;
• the Journal tool was available;
• the process reached the write step;
• the entry used the expected title;
• an error did not occur;
• the destination did not change; and
• the entry was not written to another journal.

Review Workbench Activity, RunFlows output, or Schedule Manager history.

Do not repeat the write action until you know the first attempt did not complete.

Check whether the monitor is watching the right journal

A workflow may write to a journal other than the one currently selected.

Review:

• the workflow's Journal step;
• the selected destination;
• Gene settings;
• manual tool settings;
• recent configuration changes; and
• similarly named journals.

Change the Journal Monitor selection when needed.

If a new entry does not appear immediately

Allow the workflow time to reach the Journal step.

The write may occur after:

• source collection;
• one or more AI steps;
• tool calls;
• classification;
• image generation;
• review logic; or
• final formatting.

Check RunFlows or Schedule Manager before assuming the write failed.

If the monitor appears inactive

Check that:

• Feluda remains open;
• the Journal page is available;
• Journal Monitor is open;
• a journal is selected;
• the expected process is running;
• the workflow still writes to that journal; and
• no application error is shown.

Close and reopen Journal Monitor when the interface no longer reflects new activity.

Then test it with a simple non-sensitive manual entry.

Test Journal Monitor with a manual entry

A manual entry is a useful basic test.

1. Open Journal Monitor.
2. Select a journal.
3. Create a manual entry in that same journal.
4. Save it.
5. Confirm that the entry appears in the monitor.
6. Open and review it.

If the manual entry appears, the monitor is working and the problem may be with the workflow or tool.

Test the Journal tool separately

When a workflow entry is missing, test the Journal tool in Workbench.

Use a simple request:

Use the Journal tool to create an entry titled
"Journal Monitor Test — 2026-06-08".

Write:
"This is a non-sensitive Journal Monitor test."

Review the Activity log and watch Journal Monitor.

Remove or clearly mark the test entry afterward according to your normal Journal practices.

Compare Journal Monitor with RunFlows

Journal Monitor and RunFlows answer different questions.

Area	What it shows
RunFlows	Whether the workflow ran, which steps completed, and what output appeared
Journal Monitor	Whether the selected journal received a new entry

Use both when troubleshooting a missing workflow result.

A workflow may complete without writing the Journal entry.

A Journal entry may also be written before a later workflow step fails.

Compare Journal Monitor with Schedule Manager

Schedule Manager shows whether a scheduled execution started and what happened during the run.

Journal Monitor shows whether a new entry appeared in the selected journal.

When a scheduled entry is missing:

1. check the planned run time;
2. review recent schedule history;
3. confirm whether the workflow started;
4. inspect the Journal write step;
5. confirm the destination; and
6. review Journal Monitor.

This separates a missed schedule from a failed Journal write.

Review entries before acting on them

A monitored entry may contain:

• incorrect details;
• missing information;
• unsupported claims;
• a wrong classification;
• incomplete tool results;
• an outdated source; or
• a draft that still needs approval.

Review the content before:

• sending it;
• publishing it;
• changing a record;
• making a decision;
• sharing it with a customer; or
• treating it as final.

Add visible review status

For important monitored entries, include a status in the content.

For example:

**Status:** Needs Review

Other useful values may include:

• Draft;
• Approved;
• Superseded;
• Error; or
• Completed.

The workflow should not mark an entry Approved unless a real approval process supports that status.

Monitor privacy-sensitive entries carefully

Before monitoring sensitive Journal content, check:

• who can access the computer;
• whether the screen is visible to others;
• which model processed the source;
• whether a cloud provider received it;
• which tools were involved;
• whether the correct journal was selected; and
• whether entry titles reveal private information.

Journal Monitor displays incoming activity.

Use normal device and workspace security.

Keep the monitor focused

Select one journal that matches the process you are reviewing.

Monitoring a busy journal with unrelated entries can make important results difficult to notice.

Consider separate journals or clear naming patterns for:

• project reports;
• research findings;
• security monitoring;
• customer-support reviews; or
• recurring operational summaries.

Review recurring patterns

Journal Monitor can help you notice patterns such as:

• an entry arriving late;
• a missing reporting period;
• repeated warnings;
• duplicate titles;
• changing output structure;
• shorter or incomplete entries; or
• a workflow writing more often than expected.

Record repeated problems and investigate the workflow or schedule.

Stop monitoring when it is no longer needed

Close or leave Journal Monitor when:

• the expected entry has arrived;
• the workflow is complete;
• the schedule review is finished;
• the journal is no longer relevant; or
• real-time monitoring is not necessary.

You can still browse entries normally from the Journal.

Journal Monitor is a live view, not a replacement for Journal organisation.

A practical monitoring routine

Use this process:

1. Identify the expected workflow or AI action.
2. Confirm the Journal destination.
3. Define the expected title and timing.
4. Open Journal Monitor.
5. Select the correct journal.
6. Start the workflow or wait for the schedule.
7. Review RunFlows or Schedule Manager activity.
8. Watch for the new entry.
9. Compare the title and timestamp.
10. Open and review the full content.
11. Check for missing or duplicate entries.
12. Decide whether follow-up or workflow changes are needed.

Journal Monitor helps you see new Journal activity as it happens.

Careful review determines whether that activity is correct and useful.