BA Maintenance Bridge

Task Types

These are the automated task types BA Maintenance Bridge currently generates. Tasks are meant to help you catch edge cases, follow-ups, and “something feels off” situations before they become problems.

Back to Tasks
How it works: Tasks are generated during sync. A task is visible on the Tasks page when its status is OPEN. Some tasks may be tracked as PENDING

When it’s created
During sync, for active (not completed/cancelled) melds with a vendor or management appointment whose start time is in the past (beyond the grace window).
When it shows up on Tasks
Immediately when conditions are met (status is OPEN). It may not trigger if there has been very recent activity (idle window).
How it clears
Automatically set to DONE when there is no longer a scheduled appointment, the appointment is no longer overdue, or the meld becomes completed/cancelled. Can also be manually marked Done.
Common gotchas
If someone just commented/updated the meld recently, the task is intentionally suppressed for a short period to avoid noise.
Config knobs
BA_SCHEDULED_OVERDUE_GRACE_HOURS, BA_SCHEDULED_OVERDUE_IDLE_HOURS

When it’s created
During sync, for active melds with owner_approval_status = REQUESTED/REQUESTED_ESTIMATES once the “next day at 10:00 AM” deadline passes.
When it shows up on Tasks
After the due time. Before then, it is tracked as PENDING (not shown on Tasks).
How it clears
Automatically set to DONE when owner approval is no longer requested, or the meld is completed/cancelled. Can also be manually marked Done.
Common gotchas
If the due time seems off, check the configured timezone/hour/minute. The timer starts the first time the system sees approval requested.
Config knobs
BA_OWNER_APPROVAL_FOLLOWUP_TZ, BA_OWNER_APPROVAL_FOLLOWUP_HOUR, BA_OWNER_APPROVAL_FOLLOWUP_MINUTE

When it’s created
During sync, for active melds in a responded state (approved / not approved) that are returned by the Property Meld filter ack_approval=false (meaning the response has not been acknowledged yet).
When it shows up on Tasks
Immediately when conditions are met (status is OPEN).
How it clears
Automatically set to DONE when the meld is acknowledged (drops out of ack_approval=false) or is completed/cancelled.
Common gotchas
The acknowledgement state is not exposed as a field in the meld payload; we detect it via the ack_approval query filter on /meld/.
Config knobs
BA_OWNER_APPROVAL_ACK_FETCH_LIMIT (optional)

When it’s created
During sync, for certain “pending” open meld statuses when a similar completed-like meld is found in the archive for the same address within the lookback window.
When it shows up on Tasks
Immediately when a match is found (status is OPEN).
How it clears
Automatically set to DONE when the meld is no longer in the eligible “pending” statuses, is tagged Make-Ready, has no address, or no longer has matches. Can also be manually marked Done.
Common gotchas
If the archive is empty or older than the lookback window, there may be nothing to match against. Make-Ready melds are intentionally excluded.
Config knobs
BA_TASKS_SIMILAR_RECENT_ENABLED, BA_TASKS_SIMILAR_RECENT_SCORE_THRESHOLD, BA_TASKS_SIMILAR_RECENT_MAX_MATCHES (lookback varies by maintenance bucket)

When it’s created
When completed-like melds are archived and the status is VENDOR_COULD_NOT_COMPLETE or MAINTENANCE_COULD_NOT_COMPLETE.
When it shows up on Tasks
Immediately when created (status is OPEN).
How it clears
Only clears when you mark it Done (or if the task is overwritten/updated for the same meld+type).
Common gotchas
If detail enrichment is disabled or fails, tenant/vendor names may be missing (the task still generates).
Config knobs
BA_COMPLETED_ARCHIVE_ENRICH_DETAILS (affects context quality), BA_TASKS_BACKFILL_DAYS (how far back we backfill these)

When it’s created
When completed-like melds are archived and the meld has the configured Needs Further Action tag.
When it shows up on Tasks
Immediately when created (status is OPEN).
How it clears
Only clears when you mark it Done (or if the task is overwritten/updated for the same meld+type).
Common gotchas
If the tag name changes in PropertyMeld, update BA_NEEDS_FURTHER_ACTION_TAG.
Config knobs
BA_NEEDS_FURTHER_ACTION_TAG

When it’s created
When completed-like melds are archived and a rating value is present and <= 1.0.
When it shows up on Tasks
Immediately when created (status is OPEN).
How it clears
Only clears when you mark it Done (or if the task is overwritten/updated for the same meld+type).
Common gotchas
If rating isn’t present in the payload, no task is created. Comment text may be under different keys depending on payload shape.
Config knobs
BA_COMPLETED_ARCHIVE_ENRICH_DETAILS (affects context quality), BA_TASKS_BACKFILL_DAYS (how far back we backfill these)

When it’s created
When completed-like melds are archived and a rating value is present and >= 5.0.
When it shows up on Tasks
Immediately when created (status is OPEN).
How it clears
Only clears when you mark it Done (or if the task is overwritten/updated for the same meld+type).
Common gotchas
Requires rating to be present in the archived payload. Configure BA_GOOGLE_REVIEW_URL to include a clickable link in the drafted message.
Config knobs
BA_GOOGLE_REVIEW_URL, BA_COMPLETED_ARCHIVE_ENRICH_DETAILS, BA_TASKS_BACKFILL_DAYS

When it’s created
When a meld completes and there is a linked Code Compliance inspection record for that meld id.
When it shows up on Tasks
Immediately when created (status is OPEN).
How it clears
Only clears when you mark it Done (or if the task is overwritten/updated for the same meld+type).
Common gotchas
This only triggers if the inspection is linked to the created meld (by meld id). If the inspection wasn’t linked, no task appears.
Config knobs
No direct env toggles; depends on Code Compliance workflow/records.
BART AI assistant