trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceededemail-analytics-setJobTimestamp-should-actually-insert-the-job
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    🐛 Improved reliability of email analytics events ref https://github.com/TryGhost/Ghost/pull/29890#pullrequestreview-4910616569 Big picture ----------- We sometimes failed to create the job row for the "missing" job. This could cause: - unnecessary extra fetches from Mailgun - events to be dropped entirely, if the site was off for awhile Details ------- There are four jobs for email analytics: 1. opened 2. non-opened 3. scheduled 4. missing Before this change, `setJobTimestamp` failed to upsert the job row. For the first three job types, it turned out that was fine, because they were already created by previous code paths. But not for the "missing" job! Before this change, we'd only create the "missing" job row when: - no missing events were found - there was an error processing the batch Now, we create it at the right time as intended.
    nx run ghost-monorepo:lint:boundaries
Succeeded
Linux
4 CPU cores
read-write access token used
0d7d4f7d29895

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools