Troubleshooting Data Collect trigger issues
The tab is displayed only to users who have the required Data Collect view permission for the appliances. If you do not have this permission, the tab is hidden.
The trigger action can be unavailable for several reasons:
Required permission or consent are missing.
The appliance or software version is not compatible.
Appliance connectivity is inactive or not running the required version.
A previous trigger request is still in a blocking state
The request has reached the backend rate limit.
If the page indicates that all the prerequisites are not met, reload the page and confirm that appliance information has loaded correctly before retrying. The source identifies this as a possible transient panel-load issue.
Data masking can increase generation time and may contribute to timeout conditions. If repeated timesouts occur, review the request progress details in the Activity Monitor.
After a successful submission, the trigger action remains unavailable for the rest of the current browser session for the same appliance and selected nodes.
Audit records are available for prerequisite checks and trigger actions. The trigger event is recorded as sensitive data and is visible only when the Include sensitive data filter is enables in Audit Log.