Skip to content

Sync failure leaves Cron stuck #12

Description

@tescher

Steps to reproduce

Start sync
Add in the Cron plugin and create a .py or other script that you want to run periodically
Disconnect the internet so that sync fails
See that your Cron-triggered scripts no longer run when they are supposed to
Restart Obsidian. See that Cron scripts run again

Expected result

A sync failure does not cause Cron and other scripts from running

Actual result

If Sync fails (because of a network timeout or other hiccup), it apparently hangs or keeps resources open and prevents other processes (like Cron and scripts) from running, or Cron is not detecting those resource statuses correctly

Environment

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.7.5
Operating system: Windows 11 Pro 10.0.26200
Login status: logged in
Language: en
Catalyst license: none
Insider build toggle: off
Live preview: off
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 9
Plugins enabled: 7
1: Templater v2.14.1
2: Commander v0.5.4
3: Editing Toolbar v3.1.18
4: QuickAdd v2.1.0
5: Cron v1.1.2
6: On This Day Expanded v2.0.3-fork
7: Meta Bind v1.4.6

I have several scripts that are kicked off each day by the Cron plug-in. They check for to-dos that need nudging, etc. When there is a sync issue because of a network hiccup, sync silently fails, and then I find out several days later my scripts haven’t run. When I restart Obsidian, everything is fine again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions