Skip to content

[bug] Interval reporting happens after interval update #1210

@hulto

Description

@hulto

Describe the bug
The server loses sync with the agent when interval becomes longer than previous interval eg. 5second --> 60seconds
The agent calls back retrieves the task and updates it's internal sleep but doesn't update the beacon ent's interval until the subsequent callback resulting in the beacon being marked dead.

To Reproduce
Steps to reproduce the behavior:

  1. Spin up server
  2. Spin up agent
  3. Queue the update interval tome to 60
  4. Refresh the beacon view until you see offline.

Expected behavior
Server and agent should be in sync

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtavern

    Type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions