Off-hours activity on an agent that never sleeps

What you're seeing

A Low finding on the Findings page, and a Brief line:

Off-hours activity — N actions outside declared hours (MTWTF 08:00–18:00 UTC) in the last 7 days

The count is large, often most of the agent's activity, and the Home heatmap When do the agents act shows bright cells all through the night and at weekends.

What it means

The platform compares when each agent acts with the business hours your organization declared. The default is Monday to Friday, 08:00 to 18:00 UTC. An agent that runs around the clock, or on a schedule that falls outside those hours in UTC, will trip the finding on nearly everything it does.

Two things make this common and noisy:

  • The hours are in UTC unless you set a timezone. A team working 09:00 to 18:00 in India is 03:30 to 12:30 UTC, so most of a normal working day lands outside the default window.
  • The default is a human working day. A scheduled or always-on agent has no such schedule.

The finding is Low because it is a question, not a fault: is this schedule expected?

What to do

  1. Look at the pattern first. On the Home page, Activity tab, heatmap, are the off-hours actions steady (an always-on agent) or a burst at an odd time? A burst on a sensitive system deserves a look in Investigate before you decide it is noise.

  2. If the agent is meant to run around the clock, declare it. An organization admin sets the hours under Settings, Cost tab, Business hours: pick the days, the start and end, and the time zone, then save. The same thing through the API:

    curl -X PUT https://app.provantix.tech/v1/settings/business-hours \
      -H "authorization: Bearer <token>" -H "content-type: application/json" \
      -d '{"business_hours":{"days":[1,2,3,4,5,6,7],"start":"00:00","end":"23:59","timezone":"UTC"}}'
    

    Days are ISO weekdays, 1 for Monday to 7 for Sunday. start and end must differ, so "all day" is 00:00 to 23:59. A window with start after end crosses midnight, for night shifts such as 22:00 to 06:00.

  3. If the agent follows a local working day, set the window and the timezone to match, for example 09:00 to 18:00 in Asia/Kolkata.

  4. Run reconciliation on the Findings page. The finding recounts against the new hours.

  5. Record the decision: declaring hours is written to the decision log with who set them.

What good looks like

The finding is resolved because the declared hours match how the agent really runs, and a future off-hours finding means something: an agent acting when it normally does not.

What not to do

Do not widen the hours just to make the finding go away on an agent whose off-hours activity you have not looked at. Widening hides the signal for every agent in the organization, because the hours are organization-wide.