Check system logs for error messages related to the "invalid execution id rgh" error. This can provide valuable insights into the root cause of the issue.
As a diagnostic measure, generate a brand new execution ID by initiating a new execution of the relevant process. Then immediately query the status of that new ID. invalid execution id rgh
Set up alerts for when your system attempts to access executions older than the retention policy. Use metrics to track the age of execution IDs being queried. Check system logs for error messages related to
If after all steps the error persists, and you cannot find documentation for the "RGH" token, escalate to: Then immediately query the status of that new ID
specifically for execution lookups. Avoid hardcoding IDs and always fetch the "Current Execution ID" dynamically from the environment variables provided by your runner.
Check system logs for error messages related to the "invalid execution id rgh" error. This can provide valuable insights into the root cause of the issue.
As a diagnostic measure, generate a brand new execution ID by initiating a new execution of the relevant process. Then immediately query the status of that new ID.
Set up alerts for when your system attempts to access executions older than the retention policy. Use metrics to track the age of execution IDs being queried.
If after all steps the error persists, and you cannot find documentation for the "RGH" token, escalate to:
specifically for execution lookups. Avoid hardcoding IDs and always fetch the "Current Execution ID" dynamically from the environment variables provided by your runner.
