---
title: Update Asset Headers Information (Last Intervention Date)
description: Update Asset Headers Information (Last Intervention Date)
---
[Skip to content](https://support.resnet.ai/migration/update-asset-headers-information-last-intervention-date#main-content)
English
Show submenu for translations
.jpg?width=6782&height=2762&name=primary_logo%20(1).jpg)
Open main navigation
Close main navigation
- English
Show submenu for translations
- Contact us
Contact us
How can we help you?
- There are no suggestions because the search field is empty.
1. [SUPPORT CENTER](https://support.resnet.ai/migration?hsLang=en)
2. [Workflow Automation](https://support.resnet.ai/migration/workflow-automation?hsLang=en)
3. [Example Workflows](https://support.resnet.ai/migration/workflow-automation?hsLang=en#example-workflows)
# Update Asset Headers Information (Last Intervention Date)
### ResNet Dashboard Overview
Welcome to ResNet! In this module, we’ll walk through setting up a workflow that automatically updates the Last Intervention Date on a well header whenever a workover issue is closed.
This ensures that your well records always reflect the most recent maintenance.
Let’s get started!
---
### Step 1: Setting the Trigger for Status Changes
Navigating to the Workflow Editor
First, we need to define the trigger event.
- Select Issue Status Changed as the trigger.
- This workflow will run whenever an issue’s status is updated in ResNet.
To explore more triggers, go to Quick Actions → Change Trigger Action → Type "ResNet" to see all available options.
---
### Step 2: Retrieving Issue Details
Using the Get Issue by ID Component
Since the trigger doesn’t provide all necessary details, we’ll fetch more information.
- Use the Get Issue by ID Component to retrieve full issue details.
- This helps us access key fields like Campaign ID, Asset ID, and Closed Date.
If the issue belongs to a Workover Campaign, we’ll proceed with updating the well header.
---
### Step 3: Filtering for Workover Issues
Adding a Branch Component
Now, let’s filter for closed workover issues.
- Add a Branch Component to check if:
- - Campaign Name contains "Workover"
- Issue Status = Done (meaning it’s closed)
If these conditions are met, the workflow continues. Otherwise, no updates occur.
---
### Step 4: Updating the Well Header
Using the Update Well Component
Once we confirm the issue is a closed workover, we’ll update the Last Intervention Date on the well header.
- Use the Update Well Component in ResNet.
- The only required input is the Well ID, which we retrieved earlier from the issue details.
- Set Last Intervention Date to the Issue Closed Date, ensuring the well record stays up to date.
Now, every time a workover issue is completed, the well’s last intervention date is automatically recorded.
---
### Recap & Next Steps
### That’s it! You’ve successfully set up a workflow that keeps well headers updated with the latest intervention dates.
✅ Triggers when an issue status changes
✅ Filters for closed workover issues
✅ Retrieves issue and asset details
✅ Updates the Last Intervention Date on the well header
Need more help? Check out our support documentation or reach out to our team. Happy automating!
- [ResNet For Field](https://support.resnet.ai/migration/resnet-for-field?hsLang=en)
- [ResNet For Office](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#main-content)
- [Admin](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#admin)
- [Home](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#home)
- [Assets](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#assets)
- [Issues](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#issues)
- [Campaigns](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#campaigns)
- [Resources](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#resources)
- [Field Dispatch Console](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#field-dispatch-console)
- [Gamification](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#gamification)
- [Routes](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#routes)
- [User Groups](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#user-groups)
- [Credentials](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#credentials)
- [Forms](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#forms)
- [Admin Panel](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#admin-panel)
- [Filtering](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#filtering)
- [Custom Fields](https://support.resnet.ai/migration/resnet-for-office?hsLang=en#custom-fields)
- [Integrations](https://support.resnet.ai/migration/integrations?hsLang=en)
- [Release Notes](https://support.resnet.ai/migration/release-notes?hsLang=en#main-content)
- [Feature Releases](https://support.resnet.ai/migration/release-notes?hsLang=en#feature-releases)
- [FAQs](https://support.resnet.ai/migration/faqs?hsLang=en)
- [Onboarding](https://support.resnet.ai/migration/onboarding?hsLang=en#main-content)
- [Office](https://support.resnet.ai/migration/onboarding?hsLang=en#office)
- [Field](https://support.resnet.ai/migration/onboarding?hsLang=en#field)
- [Workflow Automation](https://support.resnet.ai/migration/workflow-automation?hsLang=en#main-content)
- [Build Integrations](https://support.resnet.ai/migration/workflow-automation?hsLang=en#build-integrations)
- [Ready-to-use-components](https://support.resnet.ai/migration/workflow-automation?hsLang=en#ready-to-use-components)
- [Example Workflows](https://support.resnet.ai/migration/workflow-automation?hsLang=en#example-workflows)
- [Documentation](https://support.resnet.ai/migration/documentation?hsLang=en)
[.jpg?width=6782&height=2762&name=primary_logo%20(1).jpg)](https://support.resnet.ai/?hsLang=en)
[mailto:email@email.com](mailto:email@email.com)
Copyright © 2026, ResNet AI