# Pitfalls

Here are a few concerns to keep in mind when proposing.

### Proposal baiting

Some users post on Discord or Polymarket comments claiming that a market is ready to be proposed. They often do this to **bait others into proposing** so they can dispute it.

<figure><img src="/files/TgLaHpSpebPSqyUlrBUv" alt=""><figcaption></figcaption></figure>

### Don't go looking for proposals&#x20;

You shouldn't **go looking for markets just to propose.** Only propose when a market is **clearly ready for resolution.** Don't propose just because someone said it is.

<figure><img src="/files/RxLQJ8dZae6MILwLWWku" alt=""><figcaption></figcaption></figure>

### So what can I propose? <a href="#precedents-and-implicit-rules" id="precedents-and-implicit-rules"></a>

Occasionally, there may be markets that are **past their deadline** and ready for proposal. As always, **do your own research** before submitting.&#x20;

<figure><img src="/files/S15t0pQj8YvpEMDFpWZ2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://polymarketguide.gitbook.io/polymarketguide/resolution/how-to-participate/propose/pitfalls.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.