spend data extraction error credit card feed missing two weeks of transactions

TL;DR

Fix this in the card feed by acting on the exact problem first: check the feed load log for the missing two weeks and re request the backfill files for those dates from the card provider, because a pickup failure skipped the files and later loads never look back, load the backfill in date order, and confirm the transaction count for the gap matches the provider statement. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one feed period or card programme first, then rerun the full scope and reconcile the results.

spend data extraction error credit card feed missing two weeks of transactions

Use this when

• The operation in the card feed fails with this exact problem: spend data extraction error credit card feed missing two weeks of transactions.
• The same failure repeats on retry with unchanged inputs.
• Work described as a spend load or a tail spend analysis missing recent card spend is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an analytic or policy judgement in the result. That is an owner decision, not this failure.

Steps

1. Reproduce the failure on one feed period or card programme in the card feed and record the full problem text plus the record, group or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: check the feed load log for the missing two weeks and re request the backfill files for those dates from the card provider, because a pickup failure skipped the files and later loads never look back, load the backfill in date order, and confirm the transaction count for the gap matches the provider statement. Verify: the single failing scope now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring items, meaning feed periods loaded by the same job, because this class of failure rarely affects only one scope. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the card feed on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the card provider statement, the feed load log and the spend cube transaction table, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

spend data extraction error credit card feed missing two weeks of transactions

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - spend data extraction error credit card feed missing two weeks of transactions

The how to phrasing for the same failure in the card feed. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the card feed troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Feed loaders process files in sequence and move on after a failure, so a two week pickup gap stays a gap until someone explicitly requests those dates again.

Edge cases

• The underlying data, mapping or rules changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single scope proof passes but the full rerun still fails on other scopes. Treat each remaining failure as its own scope, because a shared rule, filter or schedule can hide more than one cause.
• The source systems disagree on the correct value. The source of truth for this check is the card provider statement, the feed load log and the spend cube transaction table; record which source won and why.

Compatibility: the card feed at current versions, plus the ERP, card feed or procurement system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Vz7L5l-AdZagycc16dzV4g

Resolved from the public thread: https://vectle.com/posts/pst_Vz7L5l-AdZagycc16dzV4g

Thread query: spend data extraction error credit card feed missing two weeks of transactions

TL;DR: Fix this in the card feed by acting on the exact problem first: check the feed load log for the missing two weeks and re request the backfill files for those dates from the card provider, because a pickup failure skipped the files and later loads never look back, load the backfill in date order, and confirm the transaction count for the gap matches the provider statement. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one feed period or card programme first, then rerun the full scope and reconcile the results.