Something Looks Wrong

Use this page when the weekly workflow stops making sense.

The goal is not to debug every symptom at once.

The goal is to locate the first dependency that failed.

That matters because the plugin is highly connected. A bad contract state can make assignments look wrong. A bad assignment can make sponsorship behavior look wrong. A bad event outcome can make finances look wrong.

If you start too far downstream, you can waste a lot of time.

Start with the First Broken Layer

Use the routing rules below.

If an expected approval or action never happened

Start with the part of the workflow that creates or receives the action.

In practice, that usually means checking:

• whether the contract offer was actually sent
• whether the receiving side already accepted or rejected it
• whether the action belongs to the driver side or the organization side

The first place to verify after that is usually Contracts.

If a driver is signed but the car still looks wrong

Start with Race Assignments.

This is one of the most common causes of weekly confusion.

A contract can be active and still not be placed on the correct car schedule.

If sponsorships look weak, missing, or inconsistent

Start with Sponsorships.

Before assuming the sponsor engine is wrong, verify:

• the correct car is selected
• the race still has open slots or active offers
• the driver is correctly assigned
• you are looking at the right race and slot

If salary, sponsor income, or costs look wrong

Start with Finances.

But do not stop there.

The next question should be:

• am I looking at the correct account?

A large amount of finance confusion comes from checking the organization account when the posting belongs to the car account, or the reverse.

If the wrong user, car, or organization context appears

Start with Organizations or Race Assignments, depending on what looks wrong.

This is usually a scope or placement problem, not a finance or sponsor problem.

If everything after the event looks wrong

Start with the event outcome itself.

Do not try to debug sponsor payouts or salary rows until you are confident the base event context is correct.

Once the event looks reasonable, move in this order:

1. Finances
2. Sponsorships
3. Contracts

That order catches the real dependency faster.

Practical Triage Examples

�I signed the driver, but I still do not have sponsorship offers.�

Start with race assignments.

The most common cause is that the driver is signed but not actually assigned to the car and race the way you intended.

�I accepted a sponsor, but I do not see the money.�

Start with finances.

Then verify:

• the correct car account
• the event actually closed
• the sponsor commitment was active and settled

�The car looks expensive this week, but I do not know why.�

Start with finances and filter the ledger by the event.

Then review the actual category mix:

• damage
• tires
• travel
• staff
• salary
• winnings share

This usually explains the problem quickly.

�The contract is there, but salary did not post.�

Start with contracts, not with sponsorships or organizations.

Verify whether the deal was active on the event date and whether the contract type actually applied to that event.

The Right Way to Troubleshoot

When the workflow breaks, use this sequence:

1. find the first layer that looks wrong
2. verify the correct scope
3. confirm the upstream dependency
4. only then review downstream effects

That is the defensible way to debug this plugin.

Final Reminder

Do not troubleshoot the whole dashboard at once.

Pick the first broken layer and work forward from there.

That is faster, cleaner, and much more likely to lead you to the real cause.